Anonymous user
Talk:Shell one-liner: Difference between revisions
→Incorrect solutions: new section
(→One Line?: I will be changing the task description back to one line to match the title. This will invalidate at least one example) |
(→Incorrect solutions: new section) |
||
Line 30:
:I will be changing the task description back to one line to match the title. This will invalidate at least one example. --[[User:Paddy3118|Paddy3118]] 08:25, 24 September 2011 (UTC)
== Incorrect solutions ==
Several examples don't make sense. I marked the C incorrect for now, but Java, first example of Go, Objeck, and PureBasic are in the same category that pipe source to a file, compile it and run the resulting exe, and I think they should all be marked incorrect, too.
Second class of incorrectness: not running from shell at all. These include AutoHotkey, ZX spectrum basic, Matlab, MUMPS, and REXX. REXX example talks about how to run an executable file which is way off topic; all others substitute "shell" with "intepreter". These, in my mind, are undoubtedly incorrect, more so than the previous category even.
There is actually a third category, where the braindead compiler/intepreter can eval a file without producing an exe but would not do so with text supplied on commandline or stdin. These include second example of Go and Oz. I'm a bit indifferent about this category, it sort of fits the spirit of the task.
Also, the "line too long" template probably can be excused from examples in this task, seeing that some languages are pretty verbose and there isn't a reliable way to break long lines across different shells. --[[User:Ledrug|Ledrug]] 20:16, 25 September 2011 (UTC)
| |||