Hi Alex,

> Hi Jon,
>
>> The script was executable (-rwxr-xr-x@), but for some reason I had to
>> replace
>> #!/usr/bin/pil
>> with this "direct" variant:
>> #!/Volumes/P3/picoLisp/bin/picolisp
>>
>> Strange, since there was no problem launcing PicoLips with
>> "/usr/bin/pil"
>> on the command line.
>
> Is there really a 'pil' script in "/usr/bin/pil"?
>
>
> BTW, I'm not really sure, but as far as I know traditionally Unix allows
> only _binary_ executables in the "#!" notation.
>
> Because of that, I always write
>
>    #!/usr/bin/picolisp /usr/lib/picolisp/lib.l
>
> as 'picolisp' is a true binary (not a script). In Linux it doesn't seem
> to matter, but I don't know how the situation is for Mac OSX.
>
> ?? Alex

Yes, using #!/usr/bin/picolisp instead of #!/usr/bin/pil worked fine in OSX.
In my case at the moment, however, this …
#!/usr/bin/picolisp /usr/lib/picolisp/lib/misc.l
… seemed to be better than .../lib.l, since the only "lib" function I
needed was 'stamp'.

Thanks for teaching me all this!

/Jon

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to