On Sep 25, 2004, at 10:27 PM, Larry Wall wrote:
On Sat, Sep 25, 2004 at 10:01:42PM -0700, Larry Wall wrote:
: We've also said that MY is a pseudopackage referring to the current
: lexical scope so that you can hand off your lexical scope to someone
: else to read (but not modify, unless you are cur
On Sat, Sep 25, 2004 at 10:01:42PM -0700, Larry Wall wrote:
: We've also said that MY is a pseudopackage referring to the current
: lexical scope so that you can hand off your lexical scope to someone
: else to read (but not modify, unless you are currently compiling
: yourself). However, random s
On Sat, Sep 25, 2004 at 02:11:10PM -0400, Chip Salzenberg wrote:
: According to Dan Sugalski:
: > At 12:25 PM -0400 9/25/04, Chip Salzenberg wrote:
: > > my $i is register;
: >
: > Except that makes things significantly sub-optimal in the face of
: > continuations, since registers aren't preserve
On Sat, Sep 25, 2004 at 11:49:26AM -0700, Jeff Clites wrote:
: >It also makes up-call lexical peeking and modification impossible.
: >This is something Larry's specified Perl 6 code will be able to do.
: >
: >That is, any routine should be able to inspect the environment of its
: >caller, and mod
> > I think Guido might have made things a
> > bit harder to separate out than you
> > anticipate, unless I misread you. It
> > appears that modules and classes are
> > also imported into the same namespace
> > as everything else in python.
>
> Yeah, I had that pointed out in private
> mail. At thi
On Sep 24, 2004, at 1:13 AM, Leopold Toetsch wrote:
Piers Cawley <[EMAIL PROTECTED]> wrote:
I could be wrong here, but it seems to me that having a special
'tailinvoke' operator which simply reuses the current return
continuation instead of creating a new one would make for rather
faster
tail call
On Sep 25, 2004, at 11:15 AM, Dan Sugalski wrote:
At 2:10 PM -0400 9/25/04, Chip Salzenberg wrote:
According to Dan Sugalski:
> Leaf subs and methods can know [their call paths], if we stipulate
that vtable methods are on their own, which is OK with me.
So, given this sub and tied $*var:
sub g
On Sep 25, 2004, at 10:14 AM, Dan Sugalski wrote:
At 7:43 PM -0700 9/24/04, Jeff Clites wrote:
On Sep 24, 2004, at 7:32 PM, Dan Sugalski wrote:
At 7:28 PM -0700 9/24/04, Jeff Clites wrote:
On Sep 24, 2004, at 6:51 PM, Aaron Sherman wrote:
However, the point is still sound, and that WILL work in P6,
At 2:10 PM -0400 9/25/04, Chip Salzenberg wrote:
According to Dan Sugalski:
> Leaf subs and methods can know [their call paths], if we stipulate
that vtable methods are on their own, which is OK with me.
So, given this sub and tied $*var:
sub getvar { my $i = rand; $*var }
the FETCH method imp
According to Dan Sugalski:
> At 12:25 PM -0400 9/25/04, Chip Salzenberg wrote:
> > my $i is register;
>
> Except that makes things significantly sub-optimal in the face of
> continuations, since registers aren't preserved...
Well, I know I'd be willing to put in a few register declarations for
i
According to Dan Sugalski:
> That is, any routine should be able to inspect the environment of its
> caller, and modify that environment, regardless of where the caller
> came from.
Understood.
> Leaf subs and methods can know [their call paths], if we stipulate
> that vtable methods are on the
At 7:43 PM -0700 9/24/04, Jeff Clites wrote:
On Sep 24, 2004, at 7:32 PM, Dan Sugalski wrote:
At 7:28 PM -0700 9/24/04, Jeff Clites wrote:
On Sep 24, 2004, at 6:51 PM, Aaron Sherman wrote:
However, the point is still sound, and that WILL work in P6, as I
understand it.
Hmm, that's too bad--it could
At Sat, 25 Sep 2004 00:53:25 -0400,
> By the way, this isn't the list for it, but it would be cool if perl6 had
> an interactive mode as good as python's. It's one of the few places I
> think python has a compelling lead.
I'm sort of partial to:
perl -MTerm::ReadLine -le '$t = new Term::ReadLine
At 12:25 PM -0400 9/25/04, Chip Salzenberg wrote:
According to Jeff Clites:
But it's nice to have stuff that a compiler can optimize away in a
standard run, and maybe leave in place when running/compiling a
debug version [...]
my $i is register;
I See A Great Need.
Except that makes things s
According to Jeff Clites:
> But it's nice to have stuff that a compiler can optimize away in a
> standard run, and maybe leave in place when running/compiling a
> debug version [...]
my $i is register;
I See A Great Need.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTE
Stephane Peiry <[EMAIL PROTECTED]> wrote:
> The solaris port does not yet support jitted vtables
Thanks, applied - as well as #31721
leo
# New Ticket Created by Stephane Peiry
# Please include the string: [perl #31720]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31720 >
The solaris port does not yet support jitted vtables (for instance function
Parrot
# New Ticket Created by Stephane Peiry
# Please include the string: [perl #31721]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31721 >
This patch implements some compare ops (eq, ne, lt, le, gt, ge on
integers - templ
18 matches
Mail list logo
