[perl #50762] AutoReply: www.parrotcode.org typo

2008-02-12 Thread Bob Rogers
While we're at it, this same page says "Participating in the meeting is by invitation only". But in today's parrotsketch, chromatic said: kj, all committers are invited. which is less exclusive than kj and I had thought. Methinks this should be clarified.

[perl #50762] www.parrotcode.org typo

2008-02-12 Thread via RT
# New Ticket Created by Bob Rogers # Please include the string: [perl #50762] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=50762 > On the http://www.parrotcode.org/misc/irclogs.html page, it says "irc.perl.log".

Re: Problem with lexical scoping

2008-02-12 Thread chromatic
On Tuesday 12 February 2008 16:55:06 Geoffrey Broadwell wrote: > Feh.  Please someone tell me there is a light at the end of this tunnel? Don't worry. Parrot will give Rakudo a whole different set of performance problems than Perl 5 has. -- c

[perl #50774] [CAGE] Build warning

2008-02-12 Thread Will Coleda via RT
On Tue Feb 12 19:07:47 2008, [EMAIL PROTECTED] wrote: > Added an explicit cast to the definition of PARROT_ASSERT, which should > resolve this error. > > On Tue Feb 12 19:00:31 2008, coke wrote: > > With recent creation of Parrot_assert(), the build now generates 2114 > > warnings of the type: > >

Re: Problem with lexical scoping

2008-02-12 Thread Geoffrey Broadwell
On Tue, 2008-02-12 at 21:36 -0500, Bob Rogers wrote: > From: chromatic <[EMAIL PROTECTED]> >Date: Tue, 12 Feb 2008 17:03:31 -0800 > >On Tuesday 12 February 2008 16:55:06 Geoffrey Broadwell wrote: > >> Feh. Please someone tell me there is a light at the end of this tunnel? > >Don

[perl #50774] [CAGE] Build warning

2008-02-12 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #50774] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=50774 > With recent creation of Parrot_assert(), the build now generates 2114 warnings of the typ

Re: Problem with lexical scoping

2008-02-12 Thread Bob Rogers
From: chromatic <[EMAIL PROTECTED]> Date: Tue, 12 Feb 2008 17:03:31 -0800 On Tuesday 12 February 2008 16:55:06 Geoffrey Broadwell wrote: > Feh.  Please someone tell me there is a light at the end of this tunnel? Don't worry. Parrot will give Rakudo a whole different set of perfor

Re: Problem with lexical scoping

2008-02-12 Thread Geoffrey Broadwell
On Tue, 2008-02-12 at 12:46 -0500, Bob Rogers wrote: > From: Andrew Parker <[EMAIL PROTECTED]> >Date: Tue, 12 Feb 2008 15:17:03 +0100 > >Thanks for the pointer, Bob. I read through it and it might be >tangentially related to this. That problem is about scopes being >modeled b

Re: Problem with lexical scoping

2008-02-12 Thread Andrew Parker
So that works in this situation because the outer lexpad that I want is the same as the caller's lexpad. Thanks for the tip :) After poking around a bit at what "getinterp" does I found some good reading. * docs/ops/core.pod - getinterp returns the ParrotInterpreter * src/pmc/parrotinterp

Re: [svn:parrot] r25665 - in trunk: include/parrot src

2008-02-12 Thread chromatic
On Tuesday 12 February 2008 04:38:34 [EMAIL PROTECTED] wrote: > Modified: >trunk/include/parrot/string_primitives.h >trunk/src/string_primitives.c > > Log: > [build] on Win32 > - fix str_dup (API_PARROT) That's weird. What outside of libparrot.dll is accessing str_dup()? This isn't a f

Re: Problem with lexical scoping

2008-02-12 Thread Patrick R. Michaud
On Mon, Feb 11, 2008 at 10:27:27PM +0100, Andrew Parker wrote: > .namespace > .sub "outer" > new $P12, "Integer" > assign $P12, 1 > .lex "x", $P12 > get_global $P18, "inner" > newclosure $P18, $P18 > $P17 = $P18() > print $P17 > print "\n" > .end > > .sub "inner" :

Re: Problem with lexical scoping

2008-02-12 Thread Bob Rogers
From: Andrew Parker <[EMAIL PROTECTED]> Date: Tue, 12 Feb 2008 15:17:03 +0100 Thanks for the pointer, Bob. I read through it and it might be tangentially related to this. That problem is about scopes being modeled by subs in parrot. IMHO there is not a great problem there,

Re: Problem with lexical scoping

2008-02-12 Thread Andrew Parker
Thanks for the pointer, Bob. I read through it and it might be tangentially related to this. That problem is about scopes being modeled by subs in parrot. IMHO there is not a great problem there, since a sub is really an abstraction for entering and leaving a scope and so a good abstract

Re: Quick config/auto/pack.pm Question

2008-02-12 Thread Ron Blaschke
James E Keenan wrote: Ron Blaschke wrote: "l" is documented as: l A signed long (32-bit) value. I'm not expert in this, so let me ask: Where is this documented other than 'perldoc -f pack'? Yes, that's where it's documented. Am I missing something obvious here? Ron