Anonymous user
Talk:Halt and catch fire: Difference between revisions
→A bit limited ?: added some more comments.
(→A bit limited ?: added some more comments.) |
|||
Line 28:
:::: But... isn't that a compilation error, as opposed to a runtime "crash"? I suspect pretty much every programming language on rc (all 800+ of them) would trigger the same. I think the task is implicitly asking for something more akin to "if 2+2<>4 then = " to compile cleanly and not crash, but "if 2+2<>5 then = " to crash, (and again implicitly) at runtime. Obviously where (the condition and) "=" is language specific. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 01:28, 16 September 2021 (UTC)
::::: Well, perhaps one could think of it as a compiler (interpreter) error, but it is more of an unexpected error that Regina REXX can't recover from. There are other errors such as a source (REXX statement) that doesn't have a closing quote or comment delimiter, or a "special" character that has no place in a REXX statement, or an unexpected left/right parenthesis or comma, etc. But this task's requirement was to make the program as short as possible (crash golf?). I tried for a concise error that (the current) Regina REXX couldn't recover from and raise the "SYNTAX" error, which a REXX program could recover from. Note that REXX can trap and possibly recover from a (statement) syntax error, and indeed, many REXX programs that have a good deal of boilerplate code that will do just that, and issue informative error messages to the terminal stating which program was being executed, which statement number failed (and how it failed), and perhaps what the particular error was (variable not defined, invalid syntax, division by zero, etc.). However, program recovery wasn't the goal for this Rosetta Code task. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 03:30, 16 September 2021 (UTC)
| |||