Hi Philipp, Arie,
> pil is just a wrapper around picolisp, it loads a few libraries etc as
Yes, but
> standard, but it relies on the intepreter being at /usr/bin/picolisp,
This is not completely correct.
Note that there are two 'pil's in the distribution: One in bin/
#!/usr/bin/picolisp /usr/lib/picolisp/lib.l
(load "@lib/misc.l" "@lib/btree.l" "@lib/db.l" "@lib/pilog.l")
which indeed calls #!/usr/bin/picolisp, but this is not meant to be called here.
It is intended to be copied to - or linked from - /usr/bin.
The other 'pil' looks different:
exec ${0%/*}/bin/picolisp ${0%/*}/lib.l @ext.l "$@"
and it is the main workhorse. It can be called locally
$ ./pil +
or with a relative or absolute path from anywhere
$ /foo/bar/pil +
and will always load everything from its local environment.
♪♫ Alex
--
UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
