Skip to main content
Code Golf

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*

11
  • 129
    \$\begingroup\$ No doubt, this deserves to win. \$\endgroup\$ Commented May 28, 2014 at 10:44
  • 92
    \$\begingroup\$ Finally, a sufficiently vigilant language for the modern age! I'm going to start using it in production. All bugs must be purged. \$\endgroup\$ Commented May 28, 2014 at 15:55
  • 15
    \$\begingroup\$ To me it seems that it is not necessarily the fault of the function that throws an uncaught exception, it could also be that the functions on the call stack are negligent for failing to catch it. It could even suggest the architecture of the whole application is flawed (Because perhaps there is no way to properly handle that exception without restructuring the code?) In short, the whole program should be deleted. \$\endgroup\$ Commented May 28, 2014 at 18:23
  • 12
    \$\begingroup\$ @JonathanPullano you're not the first one to notice that ;) \$\endgroup\$ Commented May 28, 2014 at 18:24
  • 37
    \$\begingroup\$ Additional points for swearing. A program making a confident false statement no doubt needs to be eliminated. \$\endgroup\$ Commented May 28, 2014 at 20:49