|Error-handling if your compiler had an attitude. firstname.lastname@example.org (2014-12-29)|
|Re: Error-handling if your compiler had an attitude. email@example.com (glen herrmannsfeldt) (2014-12-30)|
|Re: Error-handling if your compiler had an attitude. firstname.lastname@example.org (Walter Banks) (2014-12-30)|
|Re: Error-handling if your compiler had an attitude. email@example.com (Gene Wirchenko) (2014-12-30)|
|Re: Error-handling if your compiler had an attitude. firstname.lastname@example.org (Christophe de Dinechin) (2015-01-12)|
|From:||glen herrmannsfeldt <email@example.com>|
|Date:||Tue, 30 Dec 2014 02:57:36 +0000 (UTC)|
|Organization:||Aioe.org NNTP Server|
|Posted-Date:||29 Dec 2014 22:19:26 EST|
> What if your compiler had an attitude problem? I was thinking of funny things
> it could do for error-handling (maybe with a -X switch for GenX/Millennial
> verbose output):
> * It addresses you like "Dude! You boffed the syntax again." or the like.
> * It tells you to get glasses if you keep missing semicolons [Note 1].
> * If you use older or archaic style (particularly, deprecated stuff), it makes
> fun of you and asks if you need help with your walker. [Note 2].
has different messages that it prints on April 1st (or, at least, the
one I used to use had them) along similar lines.
Return to the
Search the comp.compilers archives again.