No, Microsoft, this information was not helpful.



  • But thanks for asking...

    Helpful question from Excel


  • sockdevs

     At least it's more useful than this:




  • The parameter is incorrect! This behavior is by design.



  • 1. It's not useful? I would think that the fact that the document failed to save is actually useful information

    2. Once again, some dumbfuck failed to use GetLastError() properly.



  • @Sir Twist said:

    1. It's not useful? I would think that the fact that the document failed to save is actually useful information

    2. Once again, some dumbfuck failed to use GetLastError() properly.

    It's too bad Microsoft didn't include GetSecondToLastError() as well. That's really what the public seems to be demanding.



  • @bridget99 said:

    @Sir Twist said:

    1. It's not useful? I would think that the fact that the document failed to save is actually useful information

    2. Once again, some dumbfuck failed to use GetLastError() properly.

    It's too bad Microsoft didn't include GetSecondToLastError() as well. That's really what the public seems to be demanding.

    GetLastErrorAndIReallyMeanErrorNotCompletionStatus()

     



  •  @RaceProUK said:

     At least it's more useful than this:


    Microsoft should troll developers by changing the "The operation completed successfully." message to "The dumbfuck developer called another function before calling GetLastError again."

     



  • @bridget99 said:

    @Sir Twist said:

    1. It's not useful? I would think that the fact that the document failed to save is actually useful information

    2. Once again, some dumbfuck failed to use GetLastError() properly.

    It's too bad Microsoft didn't include GetSecondToLastError() as well. That's really what the public seems to be demanding.

    I once tried <FONT face="courier new,courier">getAllTehErrors()</FONT> and, after quite a long time, got <FONT face="courier new,courier">OutOfMemoryException</FONT>!



  • @no laughing matter said:

    @bridget99 said:

    @Sir Twist said:

    1. It's not useful? I would think that the fact that the document failed to save is actually useful information

    2. Once again, some dumbfuck failed to use GetLastError() properly.

    It's too bad Microsoft didn't include GetSecondToLastError() as well. That's really what the public seems to be demanding.

    I once tried <font face="courier new,courier">getAllTehErrors()</font> and, after quite a long time, got <font face="courier new,courier">OutOfMemoryException</font>!

    Now, that is TRWTF, since Exceptions aren't Errors.


  • Discourse touched me in a no-no place

    @Buttembly Coder said:

    Now, that is TRWTF, since Exceptions aren't Errors.
    Yeah, but what language are we dealing with? There's plenty of subtle naming differences between Java and C# that can cause confusion in this area. The differences aren't really all that important though; just confusing.



  • @dkf said:

    @Buttembly Coder said:
    Now, that is TRWTF, since Exceptions aren't Errors.
    Yeah, but what language are we dealing with? There's plenty of subtle naming differences between Java and C# that can cause confusion in this area. The differences aren't really all that important though; just confusing.

    Obviously a .NET language, as the Java equivalent is an [code]OutOfMemoryError[/code], not an [code]OutOfMemoryException[/code]



  • @skotl said:

    Helpful question from Excel

    AAARGH!!!! Not that one!!

    The developer responsible for that deserves a whole new level of Hell specially creating for them.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.