Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Sam Ruby
Sam Ruby wrote: Consider the following code: def f(x): return len(x) for i in [0,1]: print f("foo") f = lambda x: x.upper() No, don't. Consider the following code instead: def f(x): return len(x) for i in [0,1]: print f("foo") len = lambda x: x.upper() Key differenc

Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Sam Ruby
Dan Sugalski wrote: At 7:55 AM -0400 10/18/04, Sam Ruby wrote: I've been trying to make sense of Python's scoping in the context of Parrot, and posted a few thoughts on my weblog: http://www.intertwingly.net/blog/2004/10/18/Python-Parrot-and-Lexical-Scopes While I posted it on my weblog for for

Re: Cross-compiling Parrot

2004-10-18 Thread Steve Fink
On Oct-17, Dan Sugalski wrote: > At 9:49 AM -0400 10/17/04, Jacques Mony wrote: > >Hello, > > > >I'm trying to port parrot to the unununium operating system, which > >uses a modified version of 'diet lib c'. Can anyone tell me if this > >is actually possible to force the use of this library using

Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Dan Sugalski
At 7:55 AM -0400 10/18/04, Sam Ruby wrote: I've been trying to make sense of Python's scoping in the context of Parrot, and posted a few thoughts on my weblog: http://www.intertwingly.net/blog/2004/10/18/Python-Parrot-and-Lexical-Scopes While I posted it on my weblog for formatting and linking re

Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Sam Ruby
Sam Ruby wrote: It seems like everything on that page boils down to: all functions are module-scoped closures. A closer translation: "How do I implement module-scoped closures in Parrot?" OK, I've roughed out an implementation: http://intertwingly.net/stories/2004/10/18/scopes.pir http://intertwin

Re: [perl #32035] [PATCH] tests and fixes for Integer and Undef PMCs

2004-10-18 Thread Dan Sugalski
A I have started a test script for the Integer PMC. In that process I found strangeness in get_string(). set_integer_native() can be inherited from the Scalar PMC. For the Undef PMC I fixed an error in set_number_native(). A patch is attached. The file t/pmc/integer.t is new. Applied, though the pa

Re: [perl #32022] [PATCH] push_* for resizable PMCs

2004-10-18 Thread Dan Sugalski
At 5:56 AM -0700 10/17/04, Bernhard Schmalhofer (via RT) wrote: this patch adds some relevant 'push' ops to the resizable PMCs, described in pdd_17. There are also a couple of POD improvements and tests in t/pmc/resizable*.t. Applied, thanks. -- Dan -

Re: Parrot Forth 0.1

2004-10-18 Thread Matt Diephouse
On Mon, 18 Oct 2004 17:31:05 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > > The second PIR sequence is longer. It will take > > IMCC more time to > > compile that than the first example. As the > > words become less trivial, > > this will become more true. > > But one can't weigh the

[perl #32036] [BUG] t/pmc/signal.t fails

2004-10-18 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #32036] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=32036 > I have a little smoke script I threw together that does a cvs checkout, config, make,

Re: Parrot Forth 0.1

2004-10-18 Thread Michel Pelletier
> This still doesn't seem right. The compilation > from Forth to PIR only > happens once, yes. But each time the defined > word is used, the PIR > code, which is injected, must be compiled to > bytecode. RIght. > The second PIR sequence is longer. It will take > IMCC more time to > compile that t

Re: [perl #32021] [PATCH] fix --tree option of pmc2c.pl

2004-10-18 Thread Dan Sugalski
At 5:33 AM -0700 10/17/04, Bernhard Schmalhofer (via RT) wrote: this patch fixes the --tree option of classes/pmc2s.pl. Applied, thanks. -- Dan --it's like this--- Dan Sugalski even samurai

[perl #32035] [PATCH] tests and fixes for Integer and Undef PMCs

2004-10-18 Thread via RT
# New Ticket Created by Bernhard Schmalhofer # Please include the string: [perl #32035] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=32035 > Hi, I have started a test script for the Integer PMC. In that process I foun

Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Sam Ruby
Sam Ruby wrote: Unfortunately, these PMCs don't seem to have test cases. Correction: t/pmc/sub.t - Sam Ruby

Re: Parrot Forth 0.1

2004-10-18 Thread Matt Diephouse
On Mon, 18 Oct 2004 14:17:59 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > Okay, note that the code I mentioned (the > speration of core from core words) is not > checked in right now, but the version in CVS > does do NCG. Noted. > Using the direct threading model, this does 2000 > g

Re: Parrot Forth 0.1

2004-10-18 Thread Michel Pelletier
>> I propose you and I work together to make a >> totally Forth-language agnostic Forth >> micro-kernel. This kernel can be very >> minimalistic, a stacik, a machine state hash, >> and definitions for the words "code", "next", >> "word", and "'" (tick) all having standard >> Forth >> behavior, a

Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Sam Ruby
Aaron Sherman wrote: On Mon, 2004-10-18 at 07:55, Sam Ruby wrote: I've been trying to make sense of Python's scoping in the context of Parrot, and posted a few thoughts on my weblog: http://www.intertwingly.net/blog/2004/10/18/Python-Parrot-and-Lexical-Scopes It seems like everything on that page b

Re: Python, Parrot, and lexical scopes

2004-10-18 Thread Aaron Sherman
On Mon, 2004-10-18 at 07:55, Sam Ruby wrote: > I've been trying to make sense of Python's scoping in the context of > Parrot, and posted a few thoughts on my weblog: > > http://www.intertwingly.net/blog/2004/10/18/Python-Parrot-and-Lexical-Scopes It seems like everything on that page boils down

Re: [Summary] Register stacks again

2004-10-18 Thread Matt Fowles
All~ This feels similar in spirit to the old framestacks that we used to have. I throught that we moved away from those to single frame things so that we did not have to perform special logic around continuations. I would feel more comfortable if someone explained both the initial motivation of

Re: Parrot Forth 0.1

2004-10-18 Thread Matt Diephouse
On Sun, 17 Oct 2004 22:07:11 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > This is my first chance to take a look at it but > I'm sorry I've nto been able to run it because > I'm on a different machine. I did look at the > code though. Thanks for the feedback. I don't have time to re

[Summary] Register stacks again

2004-10-18 Thread Miroslav Silovic
This is a summary of a private mail conversation between Leo and myself. No, it didn't start by me forgetting to fix Reply-To when trying to post follow-up on the list. ;) Essentially we whipped up a GC scheme for collecting the register stacks that doesn't make call/cc-using code, well, unusab

Python, Parrot, and lexical scopes

2004-10-18 Thread Sam Ruby
I've been trying to make sense of Python's scoping in the context of Parrot, and posted a few thoughts on my weblog: http://www.intertwingly.net/blog/2004/10/18/Python-Parrot-and-Lexical-Scopes While I posted it on my weblog for formatting and linking reasons, feel free to respond on the mailing

Re: Problems with 0.1.1 release on x86-64

2004-10-18 Thread Brian Wheeler
Sorry for the delay...work interfered with my playing and I had to transfer my CVS repo to my x86-64 machine. I don't know if I'd classify it as "silence thereafter..." as in the summary, but its pretty close :) Here's the diff against the current CVS. It doesn't mess with the default class tha