Re: Pil transformed

2020-04-23 Thread George-Phillip Orais
No problem ;)



On Fri, Apr 24, 2020 at 11:15 AM Jean-Christophe Helary <
jean.christophe.hel...@traduction-libre.org> wrote:

> Thank you George,
>
> > On Apr 24, 2020, at 10:39, George Orais  wrote:
>
> > Hi Jean-Christophe,
> > maybe the README file inside doc64 can help answer your question ;) one
> thing that reminds me is the namespace? The reason why is pil32 uses hash
> table for the symbol table while pil64 uses binary tree? Not so sure but
> something like that :)
>
> Ok then, way over my head then :) But thank you for the pointer :)
>
>
> Jean-Christophe Helary
> ---
> http://mac4translators.blogspot.com @brandelune
>
>
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe
>


Re: Pil transformed

2020-04-23 Thread Jean-Christophe Helary
Thank you George,

> On Apr 24, 2020, at 10:39, George Orais  wrote:

> Hi Jean-Christophe, 
> maybe the README file inside doc64 can help answer your question ;) one thing 
> that reminds me is the namespace? The reason why is pil32 uses hash table for 
> the symbol table while pil64 uses binary tree? Not so sure but something like 
> that :)

Ok then, way over my head then :) But thank you for the pointer :)


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune



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


Re: Pil transformed

2020-04-23 Thread George Orais
Hi Andras, 
this is super cool! Thanks for sharing!


Hi Jean-Christophe, 
maybe the README file inside doc64 can help answer your question ;) one thing 
that reminds me is the namespace? The reason why is pil32 uses hash table for 
the symbol table while pil64 uses binary tree? Not so sure but something like 
that :)


BR,
Geo




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


Re: Pil transformed

2020-04-23 Thread George-Phillip Orais
Hi Andras,
this is super cool! Thanks for sharing!


Hi Jean-Christophe,
maybe the README file inside doc64 can help answer your question ;) one
thing that reminds me is the namespace? The reason why is pil32 uses hash
table for the symbol table while pil64 uses binary tree? Not so sure but
something like that :)


BR,
Geo


Re: Pil transformed

2020-04-23 Thread Jean-Christophe Helary
Andras,

> On Apr 24, 2020, at 5:02, Andras Pahi  wrote:
> 
> Hi all,
> 
> I have changed the 32bit pil version written in C to compile in 64bit mode
> and to support short numbers encoded in the pointers themselves.
> That means that (== 64 64) is T for both the 32bit and the 64bit version.

Well, I tried to build it on macos 10.15 and, as far as I can tell, it works :)

I was a bit emotional when I tried so I actually ran pil by using the full 
path, and OMG it worked !!! :)

> It passes the picoLisp test suite and tankf33der’ test suite as well.
> The tests should be modified to detect this particular version with
> (and *CPU (== 64 64)) because it does not support the constructs of pil64.
> 
> No doubt pil64 still has the performance advantage, running tankf33der’s
> Test suite:
> 
> pil64 9m40s
> pil, 64bit 14m 
> pil, 32bit 18m40s
> 
> If anyone is interested the sources can be found at 
> https://github.com/pahihu/picoLisp

Is there any other thing that we'd get from pil64 and that we don't get from 
that new pil32 ? I'm not sure I understand the implications (which might as 
well mean that, hey, it should work for my purposes ;)

> Happy Lisping!

Thank you so much !!!


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune



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


Pil transformed

2020-04-23 Thread Andras Pahi
Hi all,

I have changed the 32bit pil version written in C to compile in 64bit mode
and to support short numbers encoded in the pointers themselves.
That means that (== 64 64) is T for both the 32bit and the 64bit version.

It passes the picoLisp test suite and tankf33der’ test suite as well.
The tests should be modified to detect this particular version with
(and *CPU (== 64 64)) because it does not support the constructs of pil64.

No doubt pil64 still has the performance advantage, running tankf33der’s
Test suite:

pil64 9m40s
pil, 64bit 14m 
pil, 32bit 18m40s

If anyone is interested the sources can be found at 
https://github.com/pahihu/picoLisp 

Happy Lisping!

Andras