Re: Tests in PicoLisp

[Christophe Gragnic]

On Wed, Dec 14, 2016 at 2:53 PM, Alexander Burger  wrote:
> Hi Christophe,
>
>> In lib/test.l I read:
>> «««
>> Local usage:
>> # ./pil lib/test.l -bye +
>> »»»
>>
>> Shouldn't it be
>> «««
>> bin/pil lib/test.l -bye +
>
> Not really. The bin/pil script is a template to be copied or linked to 
> /usr/bin,
> i.e. a global installation. You see it from the hashbang line
> #!/usr/bin/picolisp /usr/lib/picolisp/lib.l
>
> The "true" PicoLisp local startup is the pil script in the installation
> directory.

OK sorry, I just noticed this other pil in the meantime.

>> test:
>>  $(bin)/pil $(lib)/test.l -bye +
>
> Hmm, why is this so important? It has nothing to do with make, and runs in a
> different context.

Sometimes people use make to run tests, right after a build.
No big deal here. Thanks for your availability.


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

Re: Tests in PicoLisp

[Alexander Burger]

Hi Christophe,

> In lib/test.l I read:
> «««
> Local usage:
> # ./pil lib/test.l -bye +
> »»»
> 
> Shouldn't it be
> «««
> bin/pil lib/test.l -bye +

Not really. The bin/pil script is a template to be copied or linked to /usr/bin,
i.e. a global installation. You see it from the hashbang line
#!/usr/bin/picolisp /usr/lib/picolisp/lib.l

The "true" PicoLisp local startup is the pil script in the installation
directory.


> test:
>  $(bin)/pil $(lib)/test.l -bye +

Hmm, why is this so important? It has nothing to do with make, and runs in a
different context.

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