Stupid Compiler Messages



  • What's the stupidest/most aggravating compiler message you've seen?

     

    I submit:

    ; expected

    Previously known as "missing semi-colon".  If the compiler can figure this out then why the heck doesn't it just fix it??!



  • It knows it's missing -- but it doesn't necessarily know where. Most
    languages that use semicolon line terminations are also
    whitespace-insensitive (you can write the whole thing on one line if
    you want -- it'll compile, but you know someone will post it here
    sooner or later).



    Besides, when compared to REALLY stupid stuff like the old DOS error
    message "Keyboard not found. Press F1 to continue...", this hardly
    rates a raised eyebrow.



  • "Besides, when compared to REALLY stupid stuff like the old DOS error
    message "Keyboard not found. Press F1 to continue...", this hardly
    rates a raised eyebrow."



    i.e. when you get the keyboard reconnected...press F1 to continue...[H]



  • I don't see too many stupid ones anymore.  The aggravating ones
    are those that I cause due to coding mistakes, and the aggravation is
    with myself!



    (ie, using assignment (=) instead of comparison (==) in "if" statements, or attempts to use uninitialized values)




  • I can't remember the exact situation, but missing a ; or other token
    sometimes throws the VC6 compiler into a coniption, and causes an
    endless stream of the sam error message over and over, until the
    compiler stops because it's reached the maximum number of errors.



  • Um, no -- not "when you get the keyboard reconnected...press F1 to
    continue", since the hardware scan had been done, terminated with a
    no-reply from the keyboard, and device ports would not normally be
    rescanned at that point (at least not on the machines that I used to
    use). The actual procedure was "reconnect the keyboard and boot
    afresh...there will be no need to press F1, since this error will not
    arise". Even if the keyboard could be located on hot-plug (remember,
    nothing was hot-pluggable in the Dark Ages), the error message itself
    is indisputably stupid.



  • @Blue said:

    I don't see too many stupid ones anymore.  The aggravating ones are those that I cause due to coding mistakes, and the aggravation is with myself!

    (ie, using assignment (=) instead of comparison (==) in "if" statements, or attempts to use uninitialized values)

    I continually do:

    if(object) instead of if(object!=null)

    if(x) instead of if(x>0)

    drives me insane that I cant 😛



  • I know it's not really a compiler error, but you have to love the 'unspecified error' you can get when doing things in Javascript (in IE). [:'(]

    Drak



  • Not to mention the error you get when you run this script in IE 5+.

    <FONT face="Courier New"><HTML>
     <HEAD>
      <TITLE>Error</TITLE> 
     </HEAD>
     <BODY>
      <TABLE id="tblError"></TABLE>
      <SCRIPT language="javascript">
       document.getElementById("tblError").innerHTML = "This will cause an error.";
      </SCRIPT>
     </BODY>
    </HTML></FONT>

    Very helpful.

    Drak


Log in to reply
 

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