Re: Unified prelude, FFI, multiple runtimes

2005-09-14 Thread Yuval Kogman
On Tue, Sep 13, 2005 at 02:08:47 +0300, Yuval Kogman wrote: > A proof of concept is available here: and has been updated here: http://svn.openfoundry.org/pugs/perl5/Blondie/ There's a bit of documentation, and the code is split up into files and ever so slightly refactored. -- () Yuv

Re: Unified prelude, FFI, multiple runtimes

2005-09-12 Thread Yuval Kogman
On Mon, Sep 12, 2005 at 13:27:21 -0600, Luke Palmer wrote: > On 9/12/05, Yuval Kogman <[EMAIL PROTECTED]> wrote: > > Hi, > > Hi. These are superficial thoughts, before I've had time to really > think about the Big Picture. > > > 2. each block of code has a cryptographic digest, which is the

Re: Unified prelude, FFI, multiple runtimes

2005-09-12 Thread Yuval Kogman
A proof of concept is available here: http://svn.openfoundry.org/pugs/docs/notes/circular_prelude_stuff.pl And logs where I explain the guts to Luke are availble here: http://colabti.de/irclogger/irclogger_log/perl6?date=2005-09-12,Mon&sel=785#l1413 -- () Yuval Kogman <[EMAIL PROTECTED]> 0xE

Re: Unified prelude, FFI, multiple runtimes

2005-09-12 Thread Luke Palmer
On 9/12/05, Yuval Kogman <[EMAIL PROTECTED]> wrote: > Hi, Hi. These are superficial thoughts, before I've had time to really think about the Big Picture. > 2. each block of code has a cryptographic digest, which is the hash > of it's body with the digests of all the functions it cal

Re: Unified prelude, FFI, multiple runtimes

2005-09-12 Thread Yuval Kogman
On Mon, Sep 12, 2005 at 13:15:33 +0300, Yuval Kogman wrote: The circularity issue was not made clear in the email or the diagram. Here is what I meant: The prelude operators are mutually recursive at some point, and completely pure. An pathetic example: multi &infix:<-> (Int $x, Int $y)

Re: Unified prelude, FFI, multiple runtimes

2005-09-12 Thread Yuval Kogman
On Mon, Sep 12, 2005 at 13:15:33 +0300, Yuval Kogman wrote: > To make things safe, when the prelude is bug fixed and the runtime > is not yet updated, the cryptographic hash of the function changed, > so it is no longer equal to the native one based on the way they are > paired. It should be noted