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 ;)
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 t
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 som
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
somethi
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,
