>
> I don't know how to check whether on a rasp runs the 32bit or 64bit version
> of picolisp.
>
(unless (== 64 64)
(msg "pil64 required")
(bye 1) )
(mike)
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
On Fri, Jul 13, 2018 at 12:08:55PM +0200, O.Hamann wrote:
> Document string for (version flg) says: 'The JVM- and C-versions print an
> additional "JVM" or "C",'
>
> Am I right, that a result list like (16 12 8) signals definitely a 64bit
> picolisp version?
No, this plain list (16 12 8) is
Hi,
I usually follow the one on the readme file which suggest to do this; input the
folowing expression on the repl:
(== 64 64)
if it returns T then its running 64bit
if it returns NIL its running 32bit
Hope this helps, cheers!
BR,
geo
> On Jul 13, 2018, at 7:08 PM, O.Hamann wrote:
>
>
Document string for (version flg) says: 'The JVM- and C-versions print
an additional "JVM" or "C",'
Am I right, that a result list like (16 12 8) signals definitely a 64bit
picolisp version?
I don't know how to check whether on a rasp runs the 32bit or 64bit
version of picolisp.
Regards
On 2018-07-13 05:25, Bruno Franco wrote:
actually, you could just put the function (mumble-mumble X) in the
place
of Y:
(for X (1 2 3 4 5)
(NIL (mumble-mumble X)
(println "this does not work")) )
Sure, but this doesn't help if I wish to use Y in multiple places...
On Thu, Jul 12, 2018 at
On 2018-07-13 07:19, Alexander Burger wrote:
Hi Johan,
First off, I'm confused about what the correct way of doing local
exits.
There's no "return" or "return-from" -- instead the closest thing I've
found
is "quit", which is sort of akin to "error" in CL
Correct. There is no 'return'
