Hi all,
next Friday (Nov 6th) is PilCon again!
https://meeting.itship.ch/PilCon
As it is the first Friday of the month, we'll meet at 8:00 UTC.
Perhaps we should talk about more basic issues this time?
Any newcomer's questions should be welcome.
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@so
I am not sure if I'll be able to join, but would be good to hear about best
practices in error handling (how to catch and throw errors properly)
Regards,
Davide
On Wed, Nov 4, 2020, 12:03 Alexander Burger wrote:
> Hi all,
>
> next Friday (Nov 6th) is PilCon again!
>
>https://meeting.itship.
Hi Davide,
> practices in error handling (how to catch and throw errors properly)
Good, noted :)
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi folks,
For me the greatest obstacle in using picolisp is the lack of arrays. Let's
talk about what I'm doing wrong and why I don't need them!
Stay safe,
the other Alex
Am 4. November 2020 11:55:44 MEZ schrieb Alexander Burger
:
>Hi all,
>
>next Friday (Nov 6th) is PilCon again!
>
> https
Hi Alex,
> For me the greatest obstacle in using picolisp is the lack of arrays. Let's
> talk about what I'm doing wrong and why I don't need them!
Yes, good idea. This is a valid and common question.
Maybe, as a warm-up, you could also check "Array Abstinence" at
https://picolisp.com/wiki/?
Hi Jon,
> I have put the files into lib and misc.
This is all right.
> However, I have not installed pil21 "globally" with required symlinks. When I
This is also good. Here on my systems I haven't installed it globally either (I
usually leave the Linux distro's (older) version global as it is)
Hi Alex,
I have put the files into lib and misc. However, I have not installed pil21
"globally" with required symlinks. When I cd to my pil21 directory and then do
$ pil21 misc/cube.l
then I get this:
[misc/cube.l:6] !? (load "@lib/openGl.l")
"@lib/openGl.l" -- Open error: No such file or direct
While at it, it would be good to touch on the "interpreter only" approach
of PicoLisp. It is objectively simpler than an interpreter AND compiler
implementation. However, I would love for some expansion on the explanation
of "True equivalence of code and data". Also, is there any update to the
view
Hi Kashyap,
> While at it, it would be good to touch on the "interpreter only" approach
> of PicoLisp. It is objectively simpler than an interpreter AND compiler
> implementation. However, I would love for some expansion on the explanation
> of "True equivalence of code and data". Also, is there a
