• Mez (unregistered)

    Self referencing example...I love it! For more examples, see this.

  • Ilya (unregistered)

    The last one could easily pass for a Viking.

    "Aaaaaaag! I will CRUSH you!"

  • (cs)

    This is a superfluous comment that has no valuable information but requires the reader (you) to get all the way to the end in order to realize this post really said nothing.

    {Gratz on spelling superfluous correctly }

  • (cs)

    There is no error message. You didn't see anything. Please step into that car.

  • (cs) in reply to Ilya
    Ilya:
    The last one could easily pass for a Viking.

    "Aaaaaaag! I will CRUSH you!"

    It looks like a graphics guy* was distracted and leaned on the keyboard.

    (*In a TV studio, this is a person responsible for the "graphics" that display on the screen)

  • (cs)

    Must be a tortured NFC East fan:

    [image]
  • (cs) in reply to sootzoo
    sootzoo:
    Must be a tortured NFC East fan:

    [image]

    I am originally FROM Philadelphia. That's how we talk!!

  • (cs)

    TheDailyWTF forum readers won't see this message. No! they won't! I am quite sure of that.

  • Pl (unregistered)

    The services notice is shown by windows if you manually start a service, to keep you from wondering why it is still marked as not running in the list. Only slightly curious if you don't know the context.

  • (cs)

    The developer of the first one must've really been on something. That isn't even helpful for internal people to troubleshoot. I add in advanced options (only accessible to internals) that cause my applications to spew out all sorts of data, but that's helpful. I don't see how a dialog with that message would be of any use to anyone.

    Invisible forms with that message, however...

    Flashback. That reminds me of what I used to do in VB3 on Windows 3.1.

  • (cs)

    I'm pretty sure the first one is more likely a variant of if(foo){ doStuff(); } else if(bar){ doBarStuff(); } else{ // should never get here }

    While cerr << "!foo && !bar => OH NOES!"; would have bee preferred, I'll take DisplayMessageToUser() over the comments.

  • A Nonny Mouse (unregistered)

    depends on the keyboard really

    [image]
  • Kederaji (unregistered)

    See, the football wtf would be perfect if the QB was getting sacked.

  • Pyro (unregistered)

    you don't see this comment, in case you do see this comment pretend that you don't or else your name will be changed to AAAAGGG :)

  • (cs)

    Man, I remember seeing that Cowgirls shot! ESPN had quite a few times this season where they threw odd strings. I never thought to rewind a take a picture, tho...

  • Russ (unregistered) in reply to tmountjr
    <!--- The user won't see this comment --->
  • (cs) in reply to vt_mruhlin
    vt_mruhlin:
    I'm pretty sure the first one is more likely a variant of if(foo){ doStuff(); } else if(bar){ doBarStuff(); } else{ // should never get here }

    While cerr << "!foo && !bar => OH NOES!"; would have bee preferred, I'll take DisplayMessageToUser() over the comments.

    That is what assertions are for. Developers can see that an "impossible" condition was encountered, and users won't see it.

  • (cs) in reply to tmountjr
    tmountjr:
    Man, I remember seeing that Cowgirls shot! ESPN had quite a few times this season where they threw odd strings. I never thought to rewind a take a picture, tho...

    I think I saw the 'aaaaaaag' thing at least once in every Monday-night game this season. It was like an easter egg to look for each week. Perhaps that's the default placeholder string?

  • (cs) in reply to ParkinT

    i can see how i could lean on the 'A' key, but then hit the 'G' key accidentally? this is obviously the work of a mastermind, someone who is hacking the media and fudging players' names in an attempt to create mass hysteria and panic...

  • Walleye (unregistered)

    That's the famous quarterback, Steve Aaaaaag.

  • (cs) in reply to vt_mruhlin
    vt_mruhlin:
    I'm pretty sure the first one is more likely a variant of if(foo){ doStuff(); } else if(bar){ doBarStuff(); } else{ // should never get here }

    My guess is that the code looked like:

    if(guardCondition) ..throw new Exception("User won't see this message. Calling method will display a more appropraite message instead...");

    And then the client just did:

    showPopup(e.getMessage());

    shrug

  • (cs)

    At least for Romo it said "Aaaaaag" and not "Jessica Simpson's Lap Dog"

  • (cs) in reply to ParkinT

    The first Error'd is missing one important button:

    [FAIL]

  • (cs) in reply to Ilya
    Ilya:
    The last one could easily pass for a Viking.

    "Aaaaaaag! I will CRUSH you!"

    But he wouldn't write "Aaaaaaag", he'd just say it!

  • Ebs2002 (unregistered) in reply to Zylon
    Zylon:
    Ilya:
    The last one could easily pass for a Viking.

    "Aaaaaaag! I will CRUSH you!"

    But he wouldn't write "Aaaaaaag", he'd just say it!

    Do you suppose he was taking dictation?

  • (cs)
    Cole wondered, how many types of automatic transmission can there be?

    Well, let's see... you've got your full-auto, semi-auto, tiptronic, shiftless (continuous drive)... [[insert future technology 1 here]], [[insert future technology 2 here]]. I think that about covers it.

  • (cs)

    Isn't there a Saint Aauuuves in Dallas Cowboys?

  • M.C. Sarbanes-Oxalot (unregistered) in reply to T_PAAMAYIM_NEKUDOTAYIM

    No, no, it's Ooooogg... OOOOOOGG, at the back of the throat...

  • (cs)

    "The user won't see this message."

    Obviously, an apprentice Jedi coder.

    "You don't need to see the GUID."

    "These aren't the records you are querying for."

    --Rank


    Exceptions are not the way of the Jedi coder. Do or do not. There is no Try.

  • get Message Error(Buyer)!! (unregistered)

    get Message Error(Buyer)!!

  • (cs) in reply to ParkinT
    ParkinT:
    sootzoo:
    Must be a tortured NFC East fan:
    I am originally FROM Philadelphia. That's how we talk!!

    I think the graphic sums up my feelings on the current season. Anyone know where I can get a <!-- user cannot see this football team --> button for my TV?

  • Dave (unregistered) in reply to sootzoo

    He wouldn't bother to type 'Aaaaaaaggggg!', he'd just say it.

  • David (unregistered)

    Maybe the writer died as he was typing it. (Whoever hasn't seen Monty Python and the Holy Grail should walk away)

  • (cs)
  • (cs) in reply to Veinor
    Veinor:
    So, is that a team from Bobby's World?
  • Frost (unregistered) in reply to Walleye
    Walleye:
    That's the famous quarterback, Steve Aaaaaag.

    Perhaps the graphics guy was dying as he entered in the text.

  • David (unregistered) in reply to Frost
    Frost:
    Walleye:
    That's the famous quarterback, Steve Aaaaaag.

    Perhaps the graphics guy was dying as he entered in the text.

    I just said that -_-

  • Wark (unregistered)

    "This is what happens when you accidentally type in DisplayMesageToUser()" instead of "//"."

    It's a common mistake. I mean, the keys are like, right next to eachother.

  • (cs) in reply to Wark
    Wark:
    "This is what happens when you accidentally type in DisplayMesageToUser()" instead of "//"."

    It's a common mistake. I mean, the keys are like, right next to eachother.

    I see that you are also using the German keyboard layout.

  • (cs) in reply to ParkinT
    ParkinT:
    It looks like a graphics guy* was distracted and leaned on the keyboard.

    (*In a TV studio, this is a person responsible for the "graphics" that display on the screen)

    I don't work on a TV studio, nor am a highly paid "graphics guy" at a network station; but I usually can get the same results simply with my cat.

    -dZ.
    
  • WinMan (unregistered) in reply to ParkinT

    So this really is a real error. :)

    Essentially, the service is running in the wrong security context and doesn't have permissions to get the data it needs to run, so it has no work to do. Gotta love the error message, though...

  • KT (unregistered)

    The Message Error(Buyer)!! was gotten and then gotten again. Some Message Error(Buyer)!! is gotten automatically if they have nothing else to get, for example, the Message Error(Buyer)!!.

  • Greg (unregistered) in reply to sootzoo
  • Richard (unregistered)

    Do you think they meant Castle Aaargh? http://en.wikipedia.org/wiki/Monty_python_holy_grail

  • (cs) in reply to Richard
    Richard:
    Do you think they meant Castle Aaargh? http://en.wikipedia.org/wiki/Monty_python_holy_grail

    You're almost three hours too late on that one.

  • KNY (unregistered)

    No one noticed that if you had typed "DisplayMesageToUser()" instead of "//", you'd get a compile error? There is no "DisplayMesageToUser()" ...

  • Doctor (unregistered)

    Malkovich(Malkovich)!! Malkovich(Malkovich)!! Malkovich(Malkovich)!! Malkovich(Malkovich)!! Malkovich(Malkovich)!! Malkovich(Malkovich)!!

  • (cs)

    Has anyone made a Holy Grail reference yet? </sarcasm>

  • TwelveBaud (unregistered)

    The PL&A message is a little superfluous, but there's a reason it's there. Other services also start and then stop which gives the same error message except with that service's name replacing the first PL&A. Without it, people would either just keep clicking start ("It didn't do anything when I pushed the button! I must not have pushed it, I'll push it again.") or believe it's an error condition ("It started and then stopped? What's wrong? WHAT AREN'T YOU TELLING ME?"). That message lets them know that things may be okay and gives a representative example.

    Captcha: "ideo" ... hmm, "idio" might be more appropriate...

  • (cs) in reply to GalacticCowboy
    GalacticCowboy:
    Cole wondered, how many types of automatic transmission can there be?

    Well, let's see... you've got your full-auto, semi-auto, tiptronic, shiftless (continuous drive)... [[insert future technology 1 here]], [[insert future technology 2 here]]. I think that about covers it.

    Not to mention the various options for the placement of the selection controls... I can think of 3 without trying: Ordinary centre console placement (T-Bar) Steering column Buttons on the dash (seen this in a Ford Transit).

Leave a comment on “What Error Message?”

Log In or post as a guest

Replying to comment #:

« Return to Article