Create an executable for a program in an interpreted language: Difference between revisions
Create an executable for a program in an interpreted language (view source)
Revision as of 03:38, 11 July 2022
, 1 year ago→{{header|J}}: it's jedo() nowadays
m (→{{header|J}}: compilers are not magic, but flesh this out a bit) |
m (→{{header|J}}: it's jedo() nowadays) |
||
Line 362:
Also, under Windows, the hashbang line would be ignored, and unnecessary. For windows, there's registry entries tell windows what interpreter to use for a specific extension. So you could eliminate the first line in the above example, but you'd have to do some other work (including picking and using a specific extension).
Meanwhile, we could do something similar with compiled C. We have the option of feeding the text to the jconsole executable, or we could do what the [https://github.com/jsoftware/jsource/blob/master/jsrc/jconsole.c#L313 jconsole] executable does and link to the J shared library, calling
=={{header|Phix}}==
| |||