Are there any namespaces in 32 bit picolisp? How are local variables defined?
As transient symbols?
I am newbie in picolisp.
SJain
I'm studying 'trace in @lib.l, and I've run into a question.
I don't understand why must 'eval be called on the second number on the
case that the first number is negative. I'm especially confused by giving 1
as an argument to 'eval. That's supposed to give you the context from which
to extract the
ok, I've found a way to pass an expression to eval:
(task -5000 (* 10 100) N 0 (tty (println (inc 'N
the next step is to figure a way to use @ inside that expression
On Sun, May 16, 2021 at 7:14 PM polifemo
wrote:
> I'm studying 'trace in @lib.l, and I've run into a question.
> I don't unde
ok, now I see how to work it with '@. It refers to the value of the first
argument:
(task -5000 (/ @ 5) N 0 (tty (println (inc 'N
I guess (eval (++ Prg) 1) is the idiom to let your functions use @. Though
you have to be thoughtful of how you do it. This '@ comes from the 'when,
which is the e
Hi Alex,
I am trying to understand how big integers are stored in Picolisp. I notice
that the ASCII values of the digits are stored in some cases - for example
1234 is stored as 0x34333231. That does not look like the format that's
used always - I am going by the "> 9" references in the cod
Great! Thanks a lot for sharing all your insights!
I think all are correct.
On Sun, May 16, 2021 at 07:30:29PM -0500, polifemo wrote:
> ok, now I see how to work it with '@. It refers to the value of the first
> argument:
>
> (task -5000 (/ @ 5) N 0 (tty (println (inc 'N
>
> I guess (eval (+
Hi Kashyap,
> I am trying to understand how big integers are stored in Picolisp. I notice
> that the ASCII values of the digits are stored in some cases - for example
> 1234 is stored as 0x34333231.
Big integers are always stored in binary representation.
I think what you saw was inside a symbol
