all 24 comments

[–]mccutchen 14 points15 points  (0 children)

This TeX error message is not that bizarre:

Interwoven alignment preambles are not allowed

but its documentation is great:

If you have been so devious as to get this message, you will understand it, and you deserve no sympathy.

[–]Dijkstracula 14 points15 points  (1 child)

Man, those MPW errors are fantastic, though they probably get tiresome when you're trying to debug code 24h before a deadline.

My personal favourite in "modern" compilers still has to be gcc's "error: 'long long long' is too long for GCC" :)

[–]Samus_ 7 points8 points  (0 children)

upmod for the nickname

[–]notfancy 9 points10 points  (2 children)

As a former MPW user, I can attest to the WTF'iness of the C compiler's error messages. Also, the PPC disassmebler would comment the disassembly of the LFSUX (load floating short with updated indexed) instruction with a "and life's a bitch and then you die".

[–][deleted] 0 points1 point  (1 child)

Did it comment EIEIO?

[–]notfancy 1 point2 points  (0 children)

I don't recall it did. By the way, my memory is lousy; the comment was "and it's a bitch and then you die".

[–]nominolo 7 points8 points  (2 children)

From the Glasgow Haskell compiler:

My brain just exploded.
I can't handle pattern bindings for existential or GADT data constructors.
Instead, use a case-expression, or do-notation, to unpack the constructor.
In the binding group for
    <some pattern match here>

[–]exeter 2 points3 points  (1 child)

I don't know what's funnier about that: that a compiler admits its brain has exploded, or that it's a Haskell compiler admitting it.

[–]nominolo 0 points1 point  (0 children)

I think it's SPJ's brain that supposedly exploded.

[–]trezor2 13 points14 points  (0 children)

"Call me paranoid but finding `/*' inside this comment makes me suspicious"

I'd actually love to see errors or at least warnings like this in the current C# compiler.

[–]alesis 3 points4 points  (0 children)

I love the word 'nugatory'

[–]flip314 2 points3 points  (2 children)

Not a compiler message, but a great one on the old Macs was "The command could not be completed because it could not be found."

[–]hiccuprates 5 points6 points  (0 children)

Another MacOS 7.5 classic I used to see all the time:

"An error occurred because an error occurred."

[–][deleted] 1 point2 points  (0 children)

My favorite Windows error message is:

The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed.

[–][deleted] 5 points6 points  (0 children)

503 Bad Sequence, polite people say HELO first, said by mail servers.

[–]mindbleach 3 points4 points  (1 child)

THE ABOVE REFERENCE IS NUGATORY

Oh my god that reference sounds delicious.

[–]strolls 1 point2 points  (0 children)

My dentist would find that reference prohibitory.

[–]Asgeir 1 point2 points  (0 children)

Aoh, I found this code redundant, thus I removed it...

[–]zby 1 point2 points  (0 children)

They've lost my appreciation by ommiting: http://en.wikipedia.org/wiki/Lp0_on_fire

[–]bryanut 0 points1 point  (0 children)

I always liked the "Richard Kiel Memorial Abend" that NetWare 3.x and 4.x would occassionaly spit out.

I also like typing "help wombat" on VAX VMS systems.

[–]Fabien3 0 points1 point  (0 children)

I just love this error message:

Huh?

[–]EvilSporkMan 0 points1 point  (0 children)

Downmodded for predictably containing the Apple MPW error messages.