At 3:56 PM + 1/13/04, Tim Bunce wrote:
On Tue, Jan 13, 2004 at 10:01:32AM +0100, Leopold Toetsch wrote:
Michal Wallace <[EMAIL PROTECTED]> wrote:
> Here's my guess:
[lots of good stuff from leo]
Is there a "Parrot Architecture Overview" document that summarises
this kind of high-level view
At 1:46 PM -0500 1/13/04, Melvin Smith wrote:
At 11:18 PM 1/12/2004 -0500, Michal Wallace wrote:
On Mon, 12 Jan 2004, Luke Palmer wrote:
A continuation is one snapshot -- it never changes, it never runs.
To invoke the continuation is to take you back to that snapshot and
start running from there
At 11:18 PM 1/12/2004 -0500, Michal Wallace wrote:
On Mon, 12 Jan 2004, Luke Palmer wrote:
> A continuation is one snapshot -- it never changes, it never runs.
> To invoke the continuation is to take you back to that snapshot and
> start running from there. To invoke it a second time is exactly
>
On Tue, Jan 13, 2004 at 10:01:32AM +0100, Leopold Toetsch wrote:
> Michal Wallace <[EMAIL PROTECTED]> wrote:
>
> > Here's my guess:
>
> [lots of good stuff from leo]
Is there a "Parrot Architecture Overview" document that summarises
this kind of high-level view with links to the deeper docs?
If
Michal Wallace <[EMAIL PROTECTED]> wrote:
> A .pcc_sub isn't an object, just a little segment of the list of
> instructions.
A pcc_sub *is* an object:
find_global P0, "_the_sub"
invokecc
print "back\n"
end
.pcc_sub _the_sub:
print "in sub\n"
invoke P1
You can store it awa
#x27;s a metaphor I'm working on to try and help me
understand how to picture all this. It's not finished (see
the end). Feedback appreciated:
===
MR PARROT'S NEIGHBORHOOD
Mr Parrot lives on a very long street. Each house on the
street contains an opcode. His job is to go doo
