Talk:Shell one-liner: Difference between revisions
Content added Content deleted
(→Incorrect solutions: different meaning of utility) |
|||
| Line 47: | Line 47: | ||
:::+1 on letter vs spirit of the task. I would have thought most languages with only compilers might be better off omitting themselves from this task, but, that said, if a compiled language could start a web server with a one-line program then an example using cat piped to a compiler etc ''might'' be of use. (That utility thing you mentioned Ledrug). --[[User:Paddy3118|Paddy3118]] 03:50, 26 September 2011 (UTC) |
:::+1 on letter vs spirit of the task. I would have thought most languages with only compilers might be better off omitting themselves from this task, but, that said, if a compiled language could start a web server with a one-line program then an example using cat piped to a compiler etc ''might'' be of use. (That utility thing you mentioned Ledrug). --[[User:Paddy3118|Paddy3118]] 03:50, 26 September 2011 (UTC) |
||
:::: That does not depend much on what string eval capability is present in the language, but rather what other stuff is present on the system. Suppose you pull the full source code of Linux kernel and type <code>make && make modules && make install</code>, then proceed to claim that the most significant part of the kernel is make's one-liner power -- no you wouldn't. Would you? --[[User:Ledrug|Ledrug]] 04:17, 26 September 2011 (UTC) |
|||
==Whilst/while== |
==Whilst/while== |
||