Talk:Native shebang: Difference between revisions
Content added Content deleted
(→Problems: new section) |
|||
| Line 5: | Line 5: | ||
./myprgm.cpp</pre> |
./myprgm.cpp</pre> |
||
:At which point <tt>run_cpp_file</tt> (originally written in C++) is called to compile and run <tt>myprgm.cpp</tt>. I personally think this is abusing the purpose of a shebang; languages that aren't compiled to some binary form before being run, such as Ruby or Perl already have existing suitable shebang mechanisms (this is even mentioned as a "difficulty": "Naturally, some languages are not compiled. These languages are forced to use shebang executables from another language, eg "#!/usr/bin/env python""). Languages compiled to a binary form, on the other hand, would more naturally use Makefiles and similar to accomplish the same kind of thing, that is "run with one or two simple commands". [[User:Lue|Lue]] ([[User talk:Lue|talk]]) 02:49, 2 February 2014 (UTC) |
:At which point <tt>run_cpp_file</tt> (originally written in C++) is called to compile and run <tt>myprgm.cpp</tt>. I personally think this is abusing the purpose of a shebang; languages that aren't compiled to some binary form before being run, such as Ruby or Perl already have existing suitable shebang mechanisms (this is even mentioned as a "difficulty": "Naturally, some languages are not compiled. These languages are forced to use shebang executables from another language, eg "#!/usr/bin/env python""). Languages compiled to a binary form, on the other hand, would more naturally use Makefiles and similar to accomplish the same kind of thing, that is "run with one or two simple commands". [[User:Lue|Lue]] ([[User talk:Lue|talk]]) 02:49, 2 February 2014 (UTC) |
||
== Problems == |
|||
The intro paragraph talks of a "third language" without identifying a second language (presumably the first language is the unix shell). Why? |
|||
The C example doesn't work for me (unless a segmentation fault from script_gcc.sh can be described as "working" or a bad interpreter error from echo.c can be described as "working"). |
|||