• merc@sh.itjust.works
    2·
    2 months ago

    I hate these. You don’t need to program for very long before you see one of these. And, you get used to the idea that when it says there’s an error on a blank line, that it means something isn’t properly terminated on one of the previous lines. But, man, I hate these.

    At the very least, you’d hope that by now compilers/interpreters would be able to say “error somewhere between line 260 and 265”. Or, more usefully “Expected a closing ‘)’ before line 265, opening ‘(’ was on line 260”.

    Error on <blank line> just pisses me off because the compiler / interpreter should know that that isn’t true. Whoever wrote the compiler is a seasoned developer who has been hit by this kind of error message countless times. They must know how annoying it is, and yet…

  • Pika@sh.itjust.worksEnglish
    0·
    2 months ago

    I hate that I noticed the syntax error on line 263 before I realized what the joke was. (at least I assume that 260 contains a function with a callback meaning it is missing the closing parenthesis)

    • master5o1@lemmy.nz
      0·
      2 months ago

      My assumption is that it’s setting up an object to map element selectors -> callbacks.

      var specialElementHandlers = {
  '#editor': function() {
    return true;
  }
};

      But yeah, could be something as

      var specialElementHandlers = Object.assign({}, defaultHandlers, {
  '#editor': function() {
    return true;
  }
}; // missing closing parenthesis