On Monday 05 May 2008 13:50:51 NotFound wrote:
> On Mon, May 5, 2008 at 2:52 AM, via RT Tom Erdevig
>
> <[EMAIL PROTECTED]> wrote:
> > Parrot segfaults running this:
> > .sub _ :main
> > null S0
> > loadlib P0, S0
> > .end
> > The segfault is caused by src/dynext.c:Parrot_load_lib sett
On 2008-May-3, at 5:04 pm, John M. Dlugosz wrote:
What does this mean?
our sub outer ()
{
...
our sub inner () { ... }
}
inner; # defined?
I think this should be illegal. Nested named subs makes sense for
'my', with the rules of visibility matching the ability to clone the
closure
On Tue, May 6, 2008 at 1:23 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> The goal for 1.0 is to ship languages separately from parrot; Can we
> get a brief summary of what sort of licensing/copyright issues apply
> when the languages are removed from perl.org repository?
>
> My simplistic unders
# New Ticket Created by Will Coleda
# Please include the string: [perl #53762]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53762 >
The goal for 1.0 is to ship languages separately from parrot; Can we
get a brief summary
On Tuesday 01 April 2008 20:25:12 Seneca Cunningham wrote:
> # New Ticket Created by "Seneca Cunningham"
> # Please include the string: [perl #52396]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=52396 >
>
>
> prove -v out
On Friday 25 April 2008 10:36:02 Will Coleda wrote:
> a default build on feather is generating the following warnings:
>
> src/jit_emit.h:1725: warning: cast discards qualifiers from pointer target
> type src/jit_emit.h:1764: warning: cast discards qualifiers from pointer
> target type src/jit_emi
Tests appear to be passing steadily on a selected sample of smoke boxes,
so I'm resolving the ticket.
Jon Lang dataweaver-at-gmail.com |Perl 6| wrote:
On Mon, May 5, 2008 at 6:01 AM, John M. Dlugosz
<[EMAIL PROTECTED]> wrote:
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
No, because {...} is just a declaration. You can give a
definition later in the surrounding module/package/class.
Patch applied in r27328.
Hi,
Yes we do exist. I'm watching and waiting for Parrot to be stable enough
to continue my project. What would be *REALLY* helpful is an ongoing log
of the way that the parrot syntax is changing. At the moment if you miss
anything you have very little chance of catching up.
Cheers,
Steveg
On
On Mon, May 5, 2008 at 2:52 AM, via RT Tom Erdevig
<[EMAIL PROTECTED]> wrote:
> Parrot segfaults running this:
> .sub _ :main
> null S0
> loadlib P0, S0
> .end
> The segfault is caused by src/dynext.c:Parrot_load_lib setting
> its local lib_name variable to NULL and then passing it al
On May 5, 2008, at 2:57 PM, Patrick R. Michaud wrote:
FWIW, I suspect that Rakudo-related news (as opposed to Parrot news)
belongs in my use.perl journal posts, and that I should be the one
writing those summaries. I was doing that regularly back in Nov-Jan,
but got sidetracked and haven't got
On Mon, May 05, 2008 at 12:48:11PM -0700, Eric Wilhelm wrote:
> >I guess what I'd really like to see would be something aimed higher
> >than the p5p summaries are. It'd be something that could be
> >interesting to a wider range of readers, not just the people who care
> > about the nitty gri
# from Andy Lester
# on Monday 05 May 2008:
>But do those lurkers actually exist?
I exist (or at least, I operate under the assumption that I exist.)
>that the people who would be interested in a summary are already on
>the list.
Indeed I am on the list. But, I usually don't read anything wi
> > > Lurkers (potential contributors.) Posting it on use.perl.org (and/or
> > > various other feed sources) would reach more of us.
> > But do those lurkers actually exist? My gut says no. My gut says
> > that the people who would be interested in a summary are already on
> > the list.
I
On Monday 05 May 2008 12:17:39 Mark Glines wrote:
> [this is a resend; first one apparently didn't get through.]
>
>
> There is a TODO comment in this function, which has been there for
> quite some time. We need to figure out if this is still valid, and
> either make the change, or remove the co
# New Ticket Created by Mark Glines
# Please include the string: [perl #53754]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53754 >
[this is a resend; first one apparently didn't get through.]
There is a TODO comment in
On Mon, May 5, 2008 at 6:01 AM, John M. Dlugosz
<[EMAIL PROTECTED]> wrote:
> TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
>
> >
> > No, because {...} is just a declaration. You can give a
> > definition later in the surrounding module/package/class.
> > Within that scope there can be only one d
On Mon Jan 28 18:20:11 2008, infinoid wrote:
> On Fri Jan 25 15:10:50 2008, ajr wrote:
> > > Hi, Alan! What kind of CPU do you have? If you have an AMD Athlon XP
> > > (or something of similar lineage), I think I know what the problem is.
> > >
> > I think you've nailed it: Athlon XP-M.
>
> Hi,
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
In "24.28.1 abs" you define
our ::?CLASS multi method abs ( $x: )
I would rather nail down the return type to 'Num where {$_ >= 0}'.
The latter might also get a nice name, e.g. Abs. This in turn would
make the abs multi method/sub kind of redu
On Mon, May 05, 2008 at 10:20:30AM -0700, Stephane Payrard wrote:
> The following PIR program prints "Match". I would expect "PGE::Match".
> I don't see the reason that motivates the current behavior
>
> .sub main
>.local pmc match
>.local string s
>load_bytecode "compilers/pge/PGE.pbc
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #53750]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53750 >
The following PIR program prints "Match". I would expect "PGE::Match".
I don't see t
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #53748]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53748 >
- Forwarded message from Moritz Lenz <[EMAIL PROTECTED]> -
current (r2732
On Mon, May 05, 2008 at 09:07:27AM -0700, chromatic wrote:
> On Monday 05 May 2008 08:29:39 Andy Lester wrote:
>
> > On May 5, 2008, at 10:23 AM, Eric Wilhelm wrote:
> > > Lurkers (potential contributors.) Posting it on use.perl.org (and/or
> > > various other feed sources) would reach more of us
On Monday 05 May 2008 08:29:39 Andy Lester wrote:
> On May 5, 2008, at 10:23 AM, Eric Wilhelm wrote:
> > Lurkers (potential contributors.) Posting it on use.perl.org (and/or
> > various other feed sources) would reach more of us.
> But do those lurkers actually exist? My gut says no. My gut sa
On May 5, 2008, at 10:23 AM, Eric Wilhelm wrote:
Lurkers (potential contributors.) Posting it on use.perl.org (and/or
various other feed sources) would reach more of us.
But do those lurkers actually exist? My gut says no. My gut says
that the people who would be interested in a summary
# from Andy Lester
# on Monday 05 May 2008:
>> This presupposes that the summaries are a good thing: anyone have
>> any feedback on this point?
>
>Just wondering who the audience would be.
Lurkers (potential contributors.) Posting it on use.perl.org (and/or
various other feed sources) would rea
HaloO,
John M. Dlugosz wrote:
I posted my current work at
http://www.dlugosz.com/files/specdoc.pdf
Please look.
In "24.28.1 abs" you define
our ::?CLASS multi method abs ( $x: )
I would rather nail down the return type to 'Num where {$_ >= 0}'.
The latter might also get a nice name, e.g.
On May 5, 2008, at 8:52 AM, Will Coleda wrote:
This presupposes that the summaries are a good thing: anyone have any
feedback on this point?
Just wondering who the audience would be.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Fri May 02 19:01:58 2008, [EMAIL PROTECTED] wrote:
> Please review/apply patch attached.
Looks good, though you can do the MANIFEST.SKIP fixup separately.
Thanks.
We've had very good luck sharing the release management duties, both
in finding volunteers and documenting our process...
Is there any interest in developing the same sort of shared process
for a week in review writeup of parrotsketch, the mailing list, RT,
commits, hackathons, etc.?
If enough of
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
No, because {...} is just a declaration. You can give a
definition later in the surrounding module/package/class.
Within that scope there can be only one definition, of course.
I did not mean to use { ... } to mean declaration only, but to show
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon May 5 13:00:02 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with mo
current (r27325) rakudo doesn't allow my Int $x = undef:
echo 'my Int $x = undef' | ../../parro
t perl6.pbc
Type check failed
Reported by muixirt++
Cheers,
Moritz
--
Moritz Lenz
http://moritz.faui2k3.org/ | http://perl-6.de/
signature.asc
Description: OpenPGP digital signature
On Mon, May 05, 2008 at 02:16:30PM +0200, Moritz Lenz wrote:
> 1) Most tests have a 'use v6-alpha;' line at the top. IMHO that's a bad
> idea, because in the end we'll want to test v6, not v6-alpha (which I
> think isn't even cleanly defined). Should we s/v6-alpha/v6/g the test
> suite? I think yes
Hi,
partly in preparation for GSoC I'd like to hear a few opinions on the
test suite
1) Most tests have a 'use v6-alpha;' line at the top. IMHO that's a bad
idea, because in the end we'll want to test v6, not v6-alpha (which I
think isn't even cleanly defined). Should we s/v6-alpha/v6/g the test
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #53738]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53738 >
Hello,
after executing the command "make reallyinstall" the directory "runtime"
is
HaloO,
John M. Dlugosz wrote:
Yes. How is a snapshot different from the object?
My interpretation is that === is an equivalence relation
on a WHICH set and eqv is an equivalence relation on a
WHAT set. A "mutable value" is an element of a (n>1):1 mapping
of a subset of WHAT to a single WHICH.
HaloO,
John M. Dlugosz wrote:
What does this mean?
our sub outer ()
{
...
our sub inner () { ... }
}
inner; # defined?
No, because {...} is just a declaration. You can give a
definition later in the surrounding module/package/class.
Within that scope there can be only one definit
# New Ticket Created by Tom Erdevig
# Please include the string: [perl #53714]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53714 >
Parrot segfaults running this:
.sub _ :main
null S0
loadlib P0, S0
.end
Invok
40 matches
Mail list logo
