Re: [Bug-apl] #!apl

[Hudson Flavio Meneses Lacerda]

Hi.

Thank all you for the inputs. My remarks about #!apl go below, after
reporting a problem.



PS.: Jürgen: can you use AP100 from scripts? Example:

#!/usr/local/bin/apl --SV -q -f
100⎕SVO'SO'
SO ← 'date'
)off

On my machine, usually I get this:

«««
Svar_record_P() failed at ../Svar_DB.cc:324
Could not find svar for key 65601537 at APmain.cc:314
»»»

Apparently, 'date' is not executed; rarely, it succeeds.





Some points about executable scripts, after tests:

a)

#!/bin/bash
⍝(){ :;};exec apl -s "$0" -- "$@"
'script body'
)off

Concise and elegant, but it does not work in environments with $CHARSET
incompatible with Unicode (trying to use '⍝' as function name).


b)

#!/bin/bash
':' ⎕EA''⍝;exec apl -s "$0" -- "$@"
'script body'
)off

So far, my preferred approach. Bash takes '⍝' just as argument for
':' (the null command), thus the script can work in any $CHARSET
environment (because Unicode is interpreted only by GNU APL, not by
Bash).


c) symbolic links

ln -s `which apl` ~/bin/aplscript

It does not work. GNU APL cannot find components like APxxx.


d) aplscript as script

   Setup:

cat>~/bin/aplscript<<END
#!/bin/bash
apl -s "\$0" "\$@"
END
chmod +744 ~/bin/aplscript

   APL script:

#!/usr/bin/env aplscript
'script body'
)off

It may work, but requires the additional setup effort, not just a
simple, standard, GNU APL install.


e)

#!apl
'script body'
)off

It only works when called from apl path; that path must be in $PATH.
If "apl" is a copy or symlink inside `pwd`,
GNU APL may have problems finding libraries.
Moreover,  current directory "./" must be in $PATH
(e.g. trailing ":." or trailing ":").


Summing up: so far, I find this (below) is the best approach, because
it is simple and functional (I presume /bin/bash is popular enough for
compatibility between environments; anyway, the first line may contain
just "#!").

#!/bin/bash
':' ⎕EA''⍝;exec apl -s "$0" -- "$@"
'script body'
)off


Thanks.
Hudson