• (cs) in reply to C-Octothorpe
    C-Octothorpe:
    zunesis:
    C-Octothorpe:
    zunesis:
    Even better

    That actually is better (at least there is something being outputted as opposed to the silent scream of a caught exception), but you'll still get the compiler warning.

    I meant "better" as in "more ironic" but whatever.

    I realized that, but wasn't sure if you knew that your example (although technically wouldn't compile) was actually an improvement.

    Anyway, excuse me while I reboot my sarcasm detector...

    Make sure that you remove that pesky 'e' variable so that it builds faster when rebooting your sarcasm detector.

  • (cs) in reply to dohpaz42
    dohpaz42:
    boog:
    Embarassingly enough, it eluded everybody that every error and exception would endure even after eliminating the pesky "e".
    BUT, the point was not to fix the errors/exceptions, it was simply to remove the build warnings.
    True, but I do have to point out that the article gives absolutely no indication that any end user ever complained about build warnings. So I do have to wonder why the developer's "solution" wasn't devised to fix the problems that the customer actually reported.

    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

  • (cs) in reply to hoodaticus
    hoodaticus:
    Yeah, I'm about as enterprisey as it gets. I've discovered that my code gets more maintainable when I have proper abstraction and domain models that describe my problems. And I've never seen non-enterprisey code that can read records from a database and package them into business objects, with exception logging, in a single line.
    Depends on how long you are prepared your lines to be.
  • (cs) in reply to boog

    try {

    boog:
    dohpaz42:
    boog:
    Embarassingly enough, it eluded everybody that every error and exception would endure even after eliminating the pesky "e".
    BUT, the point was not to fix the errors/exceptions, it was simply to remove the build warnings.
    True, but I do have to point out that the article gives absolutely no indication that any end user ever complained about build warnings. So I do have to wonder why the developer's "solution" wasn't devised to fix the problems that the customer actually reported.

    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    } catch (Exception) { } finally { // @TODO: Fix-up for a future version }

  • (cs) in reply to dohpaz42
    dohpaz42:
    C-Octothorpe:
    zunesis:
    C-Octothorpe:
    zunesis:
    Even better

    That actually is better (at least there is something being outputted as opposed to the silent scream of a caught exception), but you'll still get the compiler warning.

    I meant "better" as in "more ironic" but whatever.

    I realized that, but wasn't sure if you knew that your example (although technically wouldn't compile) was actually an improvement.

    Anyway, excuse me while I reboot my sarcasm detector...

    Make sure that you remove that pesky 'e' variable so that it builds faster when rebooting your sarcasm detector.

    Well, that was the problem! I'm releasing a hotfix that will appropriately handle that problem.

    catch(SarcasmOutOfBoundsExceptions) {
      // There! Thats better...
    }
  • (cs) in reply to boog
    boog:
    dohpaz42:
    boog:
    Embarassingly enough, it eluded everybody that every error and exception would endure even after eliminating the pesky "e".
    BUT, the point was not to fix the errors/exceptions, it was simply to remove the build warnings.
    True, but I do have to point out that the article gives absolutely no indication that any end user ever complained about build warnings. So I do have to wonder why the developer's "solution" wasn't devised to fix the problems that the customer actually reported.

    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    I see we share the same mechanic... And that he likes his corn.

  • zunesis (unregistered) in reply to boog
    boog:
    I do have to point out that the article gives absolutely no indication that any end user ever complained about build warnings. So I do have to wonder why the developer's "solution" wasn't devised to fix the problems that the customer actually reported.

    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    "...And thus the general clean-up began..."

    Addressing compiler warnings was part of a general cleanup that involved address customer-reported problems that was prompted by customer-reported problems.

  • CoderHero (unregistered) in reply to frits
    frits:
    All this talk about "e" is going to attract all of those discotheque-crazy Europeans from yesterday's comment thread.
    I thought the disco's and the trancers always wanted something called "x"
  • (cs) in reply to CoderHero
    CoderHero:
    frits:
    All this talk about "e" is going to attract all of those discotheque-crazy Europeans from yesterday's comment thread.
    I thought the disco's and the trancers always wanted something called "x"

    You are so far behind the times man. E is the new term, x is so 90's.

  • zunesis (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    boog:
    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    I see we share the same mechanic... And that he likes his corn.

    That's nothing!

    Mine shoves it in the air duct so it bakes in the summer heat, and then I turn on the AC.....

    ....The horrid smell causes me to throw up all over myself, and since I'm not watching were I'm going, I run into a pole and smack my face on the steering wheel and start bleeding....

    ...so there I am, bleeding, covered in vomit and smelling like shit in the middle rush-hour traffic right in front of my buddies from work and the hot chick from HR. The whole situation is so embarrassing I start sobbing uncontrollably....

    ...so there I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl when a cop pulls me over. At that point I just feel so alone in the world that I want to get out and give him a hug, but he doesn't want to come anywhere near me or my shitty-smelling car so he just sticks his taser out his car's window and zaps me from thirty feet away while finishing his coffee...

    ...so here I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl in a holding cell with some really hairy guy giving me eyes and this is my only phone call I get - PLEASE HELP!

  • zunesis (unregistered) in reply to KattMan
    KattMan:
    CoderHero:
    frits:
    All this talk about "e" is going to attract all of those discotheque-crazy Europeans from yesterday's comment thread.
    I thought the disco's and the trancers always wanted something called "x"

    You are so far behind the times man. E is the new term, x is so 90's.

    You are so far behind the times man. Krokodil is the new thing, "E" is so 10's

  • (cs) in reply to zunesis
    zunesis:
    boog:
    I do have to point out that the article gives absolutely no indication that any end user ever complained about build warnings. So I do have to wonder why the developer's "solution" wasn't devised to fix the problems that the customer actually reported.

    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    "...And thus the general clean-up began..."

    Addressing compiler warnings was part of a general cleanup that involved address customer-reported problems that was prompted by customer-reported problems.

    "of course, we're still rife with 'unexpected behaviors', but at least there won't be any build warnings..."

    I stand by my unpleasant analogy.

  • samspot (unregistered)

    I think I work at this company... :(

  • zunesis (unregistered) in reply to boog
    boog:
    zunesis:
    boog:
    I do have to point out that the article gives absolutely no indication that any end user ever complained about build warnings. So I do have to wonder why the developer's "solution" wasn't devised to fix the problems that the customer actually reported.

    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    "...And thus the general clean-up began..."

    Addressing compiler warnings was part of a general cleanup that involved address customer-reported problems that was prompted by customer-reported problems.

    "of course, we're still rife with 'unexpected behaviors', but at least there won't be any build warnings..."

    I stand by my unpleasant analogy.

    The developers didn't make things messier by removing compiler warnings, they just though that removing the warning would fix the problem (maybe).

    It's more like the mechanic doesn't know what to do, so he just takes the vehicle to a car wash.

    On the other hand, the shitting in the back seat does make for more interesting discussion.

  • Akers (unregistered)

    appellatio - blowing an apple?

  • (cs) in reply to zunesis
    zunesis:
    On the other hand, the shitting in the back seat does make for more interesting discussion.

    Hey I got to drop a log, where are you parked?

  • (cs) in reply to zunesis
    zunesis:
    ...so here I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl in a holding cell with some really hairy guy giving me the hug I so badly wanted and this is my only phone call I get - PLEASE SEND LUBE!

    FTFY

  • ExceptionHandler (unregistered) in reply to hoodaticus
    hoodaticus:
    zunesis:
    hoodaticus:
    The Nerve:
    Fixed?
    try { 
        DoProcessReceipts();
    }
    catch (Exception e) { 
      Console.WriteLine("Error");
    }
    
    FTFY
    Even better
    You still get the warning that way, dummy. It should obviously be:
    try { 
        DoProcessReceipts();
    }
    catch (Exception e) { 
      MsgBox(e.ToString());
    }
    
    ...especially on a server.

    But if there is an error, dont you want to retry till it works?

    public void TheProcess() {
      try { 
          DoProcessReceipts();
      }
      catch (Exception e) { 
        MsgBox(e.ToString());
        TheProcess();
      }
    }
    
  • (cs) in reply to ExceptionHandler
    ExceptionHandler:
    But if there is an error, dont you want to retry till it works?
    public void TheProcess() {
      try { 
          DoProcessReceipts();
      }
      catch (Exception e) { 
        MsgBox(e.ToString());
        TheProcess();
      }
    }
    
    ?

    But how do you get out of the never ending recursion? Stack overflow baby! Yeah!

  • (cs) in reply to Gary
    Gary:
    I use this pattern all the time in javascript. Maybe I'm looping through an array and want to do something (call methods, change properties) that only some of the elements have. I'm too lazy to inspect each one, so I'll just try and catch.
    TRWTF is Javascript. So ugly, so necessary.
  • Gone for a While (unregistered)

    Hey, did Alex stop doing the blue comments or what?

  • (cs) in reply to Gone for a While
    Gone for a While:
    Hey, did Alex stop doing the blue comments or what?

    No, it's just that nobody here posts comments that are worth blueing.

  • Gone for a While (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    Gone for a While:
    Hey, did Alex stop doing the blue comments or what?

    No, it's just that nobody here posts comments that are worth blueing.

    That's not true. I've read several here today that made me spew green tea out my oral orifice. And I was drinking coffee!

  • Akers (unregistered)

    Captcha: acsi - Acsi stupid question, get a stupid Ansi

  • SG_01 (unregistered)

    TRWTF is Exceptions, they slow down your code severely ^^ turns off RTTI

  • zunesis (unregistered) in reply to Gone for a While
    Gone for a While:
    That's not true. I've read several here today that made me spew green tea out my oral orifice.

    And I was drinking coffee!

    So the comments are so disgusting that you threw up the green tea you drank earlier?

  • Ben Dover (unregistered) in reply to Gone for a While
    Gone for a While:
    That's not true. I've read several here today that made me spew green tea out my oral orifice.

    It's not your oral orifice I'm interested in. Come here, pretty!

  • Anonymous (unregistered) in reply to StupidTheKid

    Wow! Perhaps there would also be a market for an automated warning removal tool. Though I would be ashamed to write such a thing.

  • (cs) in reply to zunesis
    zunesis:
    Gone for a While:
    That's not true. I've read several here today that made me spew green tea out my oral orifice.

    And I was drinking coffee!

    So the comments are so disgusting that you threw up the green tea you drank earlier?

    That sounds about right...

  • (cs) in reply to KattMan
    KattMan:
    ExceptionHandler:
    But if there is an error, dont you want to retry till it works?
    public void TheProcess() {
      try { 
          DoProcessReceipts();
      }
      catch (Exception e) { 
        MsgBox(e.ToString());
        TheProcess();
      }
    }
    
    ?

    But how do you get out of the never ending recursion? Stack overflow baby! Yeah!

    Oh, came-on. Of course the stack overflow will raise an exception. You hadle the exception then (the snipet already showed how to handle exceptions).

    You, people, miss the obvious.

  • zunesis (unregistered) in reply to Mcoder
    Mcoder:
    Oh, came-on. Of course the stack overflow will raise an exception. You hadle the exception then (the snipet already showed how to handle exceptions).

    You, people, miss the obvious.

    StackOverflowException Class

    ...

    Version Considerations

    In prior versions of the .NET Framework, your application could catch a StackOverflowException object (for example, to recover from unbounded recursion). However, that practice is currently discouraged because significant additional code is required to reliably catch a stack overflow exception and continue program execution.

    Starting with the .NET Framework version 2.0, a StackOverflowException object cannot be caught by a try-catch block and the corresponding process is terminated by default. Consequently, users are advised to write their code to detect and prevent a stack overflow. For example, if your application depends on recursion, use a counter or a state condition to terminate the recursive loop. Note that an application that hosts the common language runtime (CLR) can specify that the CLR unload the application domain where the stack overflow exception occurs and let the corresponding process continue. For more information, see ICLRPolicyManager Interface and Hosting Overview.

    Windows 95, Windows 98, Windows 98 Second Edition, Windows Millennium Edition Platform Note: A thrown StackOverflowException cannot be caught by a try-catch block. Consequently, the exception causes the process to terminate immediately.

    PS: RTFM

  • (cs) in reply to Mcoder
    Mcoder:
    KattMan:
    ExceptionHandler:
    But if there is an error, dont you want to retry till it works?
    public void TheProcess() {
      try { 
          DoProcessReceipts();
      }
      catch (Exception e) { 
        MsgBox(e.ToString());
        TheProcess();
      }
    }
    
    ?

    But how do you get out of the never ending recursion? Stack overflow baby! Yeah!

    Oh, came-on. Of course the stack overflow will raise an exception. You hadle the exception then (the snipet already showed how to handle exceptions).

    You, people, miss the obvious.

    You can't catch a stack overflow (at least not in .net). It's funny that in trying to make the code worse, some people unintentionally make it better...

  • zunesis (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    zunesis:
    ...so here I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl in a holding cell with some really hairy guy giving me the hug I so badly wanted and this is my only phone call I get - PLEASE SEND LUBE!

    FTFY

    Ha ha! I'm so glad we're friends again, C-Octo.

    You complete me.

  • C-Octothorpe (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    Mcoder:
    KattMan:
    ExceptionHandler:
    But if there is an error, dont you want to retry till it works?
    public void TheProcess() {
      try { 
          DoProcessReceipts();
      }
      catch (Exception e) { 
        MsgBox(e.ToString());
        TheProcess();
      }
    }
    
    ?

    But how do you get out of the never ending recursion? Stack overflow baby! Yeah!

    Oh, came-on. Of course the stack overflow will raise an exception. You hadle the exception then (the snipet already showed how to handle exceptions).

    You, people, miss the obvious.

    You can't catch a stack overflow (at least not in .net). It's funny that in trying to make the code worse, some people unintentionally make it better...

    I'm actually speaking out of school here. I don't know the first thing about funny. I do know how to be the number one poster (in volume) on TDWTF articles, though.

    Yay me.

  • (cs) in reply to Severity One
    Severity One:
    hoodaticus:
    Yeah, I'm about as enterprisey as it gets. I've discovered that my code gets more maintainable when I have proper abstraction and domain models that describe my problems. And I've never seen non-enterprisey code that can read records from a database and package them into business objects, with exception logging, in a single line.
    Depends on how long you are prepared your lines to be.
    1920 pixels, dude!

    DbConnection.ForEach("SELECT * FROM blah WHERE key=@key", r=>{/do stuff to each record here/}, new SqlParameter("@key", key);

  • (cs) in reply to hoodaticus
    hoodaticus:
    Severity One:
    hoodaticus:
    Yeah, I'm about as enterprisey as it gets. I've discovered that my code gets more maintainable when I have proper abstraction and domain models that describe my problems. And I've never seen non-enterprisey code that can read records from a database and package them into business objects, with exception logging, in a single line.
    Depends on how long you are prepared your lines to be.
    1920 pixels, dude!

    DbConnection.ForEach("SELECT * FROM blah WHERE key=@key", r=>{/do stuff to each record here/}, new SqlParameter("@key", key);

    Is the "do stuff to each record here" i++, because if it is, I think I've seen your work here before. :P

  • Sock Puppet 5 (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    hoodaticus:
    Severity One:
    hoodaticus:
    Yeah, I'm about as enterprisey as it gets. I've discovered that my code gets more maintainable when I have proper abstraction and domain models that describe my problems. And I've never seen non-enterprisey code that can read records from a database and package them into business objects, with exception logging, in a single line.
    Depends on how long you are prepared your lines to be.
    1920 pixels, dude!

    DbConnection.ForEach("SELECT * FROM blah WHERE key=@key", r=>{/do stuff to each record here/}, new SqlParameter("@key", key);

    Is the "do stuff to each record here" i++, because if it is, I think I've seen your work here before. :P

    I'm pretty sure that both of these statements indicate why neither of you have a job.

  • (cs) in reply to zunesis
    zunesis:
    Mcoder:
    Oh, came-on. Of course the stack overflow will raise an exception. You hadle the exception then (the snipet already showed how to handle exceptions).

    You, people, miss the obvious.

    StackOverflowException Class

    ...

    Version Considerations

    In prior versions of the .NET Framework, your application could catch a StackOverflowException object (for example, to recover from unbounded recursion). However, that practice is currently discouraged because significant additional code is required to reliably catch a stack overflow exception and continue program execution.

    Starting with the .NET Framework version 2.0, a StackOverflowException object cannot be caught by a try-catch block and the corresponding process is terminated by default....

    PS: RTFM

    Yeah, I should have RTFM! I couldn't imagine one could actualy catch a stack overflow at earlier versions of .Net.

    Sorry, I was trying to write nonsense, I couldn't expect reality to comply.

  • (cs) in reply to zunesis
    zunesis:
    C-Octothorpe:
    boog:
    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    I see we share the same mechanic... And that he likes his corn.

    That's nothing!

    Mine shoves it in the air duct so it bakes in the summer heat, and then I turn on the AC.....

    ....The horrid smell causes me to throw up all over myself, and since I'm not watching were I'm going, I run into a pole and smack my face on the steering wheel and start bleeding....

    ...so there I am, bleeding, covered in vomit and smelling like shit in the middle rush-hour traffic right in front of my buddies from work and the hot chick from HR. The whole situation is so embarrassing I start sobbing uncontrollably....

    ...so there I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl when a cop pulls me over. At that point I just feel so alone in the world that I want to get out and give him a hug, but he doesn't want to come anywhere near me or my shitty-smelling car so he just sticks his taser out his car's window and zaps me from thirty feet away while finishing his coffee...

    ...so here I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl in a holding cell with some really hairy guy giving me eyes and this is my only phone call I get - PLEASE HELP!

    Er, okay, I have a razor you can lend him (his hairiness seems to upset you), that may enhance the experience for you ...

  • (cs) in reply to Anonymous
    Anonymous:
    Wow! Perhaps there would also be a market for an automated warning removal tool. Though I would be ashamed to write such a thing.
    Ashamed? Or financially-endowed?
  • zunesis (unregistered) in reply to Matt Westwood
    Matt Westwood:
    zunesis:
    C-Octothorpe:
    boog:
    That's like hiring a mechanic to fix your car, but instead he just shits in the back seat.

    I see we share the same mechanic... And that he likes his corn.

    That's nothing!

    Mine shoves it in the air duct so it bakes in the summer heat, and then I turn on the AC.....

    ....The horrid smell causes me to throw up all over myself, and since I'm not watching were I'm going, I run into a pole and smack my face on the steering wheel and start bleeding....

    ...so there I am, bleeding, covered in vomit and smelling like shit in the middle rush-hour traffic right in front of my buddies from work and the hot chick from HR. The whole situation is so embarrassing I start sobbing uncontrollably....

    ...so there I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl when a cop pulls me over. At that point I just feel so alone in the world that I want to get out and give him a hug, but he doesn't want to come anywhere near me or my shitty-smelling car so he just sticks his taser out his car's window and zaps me from thirty feet away while finishing his coffee...

    ...so here I am, bleeding, covered in vomit and smelling like shit, and crying like a little girl in a holding cell with some really hairy guy giving me eyes and this is my only phone call I get - PLEASE HELP!

    Er, okay, I have a razor you can lend him (his hairiness seems to upset you), that may enhance the experience for you ...

    Well, if it's going to happen ("It's going to happen" he said) he might as well be definitely male so it doesn't confuse me latter in life, amirite?

  • zunesis (unregistered) in reply to boog
    boog:
    Anonymous:
    Wow! Perhaps there would also be a market for an automated warning removal tool. Though I would be ashamed to write such a thing.
    Ashamed? Or financially-endowed?
    ...And with that money, maybe you could get an operation and be so well endowed as to be able to make a woman out of yourself. Then you could be the fucker and the fuckee - it's the ultimate in masturbation!
  • (cs) in reply to zunesis
    zunesis:
    boog:
    Anonymous:
    Wow! Perhaps there would also be a market for an automated warning removal tool. Though I would be ashamed to write such a thing.
    Ashamed? Or financially-endowed?
    ...And with that money, maybe you could get an operation and be so well endowed as to be able to make a woman out of yourself. Then you could be the fucker and the fuckee - it's the ultimate in masturbation!

    Oh wow, dude. Wrong forum...

  • zunesis (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    zunesis:
    ...And with that money, maybe you could get an operation and be so well endowed as to be able to make a woman out of yourself. Then you could be the fucker and the fuckee - it's the ultimate in masturbation!
    Oh wow, dude. Wrong forum...
    Why won't you love me?!?!?!?!
  • zunesis (unregistered) in reply to Mcoder
    Mcoder:
    Oh, [I] came-on [myself]. Of course the stack [of] overflow[ing] [shit] will raise [my] exception[al] [penis]. You [get straped in the sad]dle [and] the exception[al penis] then snipe[s you in the ass, wait I] already showed [you] how to handle [my] exception[al penis]).

    You [lovely] people, miss [my] ob[long dong].

  • zunesis (unregistered) in reply to boog
    boog:
    True, but I do have to [eat] out that [ug-a-mug mother of mine] art[fully, she] gives absolutely no indication [when] any end [to her] ever[-flowing stream of cum, but] complain[s] about [arthritis] [without] warning. So I do have to wonder why [my mom's] "[final] solution" wasn't devised to fix the [sexual identity] problems that [her son (ME!!!)] actually reported.

    That's like hiring a mechanic to fix your car, but instead [s]he just shits [o]n the back [of your head].

  • (cs) in reply to Justice
    Justice:
    C-Octothorpe:
    the silent scream of a caught exception

    Is that a concept from Lovecraft-Driven Development (LDD)?

    Come to think of it, the majority of code seems to be based on primal terror.

    +1 What a fucking excellent idea for a new programming paradigm. I use the Burroughs Nova Express IDE myself, that chops your codebase into little pieces & sticks them back together in a random order, then administers a large dose of the opiate of your choice.

  • Martin D (unregistered) in reply to boog
    boog:
    Embarassingly enough, it eluded everybody that every error and exception would endure even after eliminating the pesky "e".
    [image]
  • Anonymous (unregistered) in reply to boog
    boog:
    Anonymous:
    Wow! Perhaps there would also be a market for an automated warning removal tool. Though I would be ashamed to write such a thing.
    Ashamed? Or financially-endowed?
    Both
  • HP PhaserJet (unregistered) in reply to Martin D
    Martin D:
    boog:
    Embarassingly enough, it eluded everybody that every error and exception would endure even after eliminating the pesky "e".
    [image]

    I, for one, prefer to have jokes explained to me.

Leave a comment on “The Pesky "e"”

Log In or post as a guest

Replying to comment #:

« Return to Article