4 ms·
Macro is okay. Procedure is not okay. Break is a procedure.
by guard-of-terra 15y ago
Macro is okay. Procedure is not okay. Break is a procedure.
- lucian1900 15y agoWhy is it not okay? Any lisper will tell you using a function is always preferable to using a macro, if at all possible.
- guard-of-terra 15y agoC is a strict and beautiful. Pascal is "Here you have your ugly break; because you too weak to live without it".
- adestefan 15y agoIf you think C is strict, then you've never looked at the ANSI C standard.
- guard-of-terra 15y agoI've looked at Delphi, thank you.
- pjmlp 15y agoYes, I have a collection of works of art entitled "buffer exploit", placed next to the "dangling pointer" exhibition hall. It is sooo beautiful.
- masklinn 15y agoDon't you understand the sheer beauty of the undefined behavior? It is not the beauty of a great painting, it's the beauty of the winter mountain: shining, tantalizing, with the stability of a marble on a needle and ready to take your life at the lightest sneeze.
- zvrba 15y agoPascal has had labeled goto from its conception. Break is just an extension / syntactic convenience. Even in C and C++ i still use goto when I have to break out of multilevel loops.
- masklinn 15y ago> Macro is okay. Procedure is not okay. Break is a procedure. Why do you believe this to matter? Smalltalk's signaling and exception handling (both `catch` and `finally` equivalent) uses regular messages and blocks (with hooks into the interpreter obviously). What value do you see in making special syntax things which need not be so, ease of "optimizations" (such as compiling a block to a jump)?