Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Is it meaningful to continue on after you get a syntax warning? Commented Nov 13, 2015 at 15:17
  • @MichaelT Well, if it so happens that the faulty code doesn't run anyway, your algorithm can still execute without problems, and you can repair it after the execution. I figure it could be very useful for debugging, but I'm worried about possible abuse/misuse of this 'feature'. Commented Nov 13, 2015 at 19:15
  • Or you could continue on and generate completely incorrect values. Which returns to "is it meaningful to continue?" What is the worst thing that can happen if you get an incorrect answer and warnings (that are ignored)? If this is a minor inconvenience - that's one thing. If it is controlling life support equipment or the message on the front page of an important site, that's another. What are the repercussions of the code "working"? Commented Nov 13, 2015 at 19:18
  • 2
    I'm voting to reopen/migrate this question because it appears to deserve a proper answer, but possibly from an audience with stronger expertise with compiler and language design. Also, it might be the case it is too broad, but this is not for us (i.e. it is only proper for people with that expertise) to decide. Commented Dec 19, 2015 at 17:39
  • 1
    I've never found "fail late" behaviour anything but really angering (a complete compile with compile time errors is like a free [if only partially complete] test suite). Fail late code has a much higher chance of getting into production and being hard to diagnose Commented Dec 19, 2015 at 19:35