Bob Rogers wrote:
I'm sorry, but I'm still seeing the same syndrome in r8070, segfaulting
in the same place, though now for only a subset of *.pbc files . . .
Yet another uninitialized pointer variable - fixed.
-- Bob
Thanks for reporting.
BTW could you/someone make a test for disassemble, to
On Wed, May 11, 2005 at 06:09:00PM -0400, Dino Morelli wrote:
> >Feel free to correct 'no_plan'. I'll happily apply any and all
> >patches to the tests, and those with commit privs are welcome
> >to directly modify the t/p6rules/*.t files at any time.
> >
>
> Speak of the devil -- I started worki
Nick Glencross wrote:
Having looked into it a little further, it actually looks like the 'ord'
operation is a significant part of the (JIT) run, perhaps as much as
50%, which seems disproportionately high... (you can just comment out
the ord to see this)
Yeah, string_ord() isn't really fast, but
Robert has migrated ponie to subversion:
http://svn.perl.org/ponie/
http://svn.perl.org/viewcvs/ponie/
I've RTFM and then tweaked the svn:external property so that
svn co http://svn.perl.org/ponie/trunk ponie
will automatically check out parrot's trunk in the right place.
For me it pass
Jerry Gay <[EMAIL PROTECTED]> wrote:
> i'm converting many of the remaining internal_exception() calls to
> real_exception() (except unimplemented ops, and other valid internal
> exceptions)
Fine, thanks - applied.
Just curious: what's the difference between these two:
E_IndexError,
Leo,
Wow! That's quite a bit of JIT code that you've just rustled up! I'll have to
wait until this evening before I can properly try it, but those results look
real good! I guess comparison with the XS version is the 'fairest' (similar
executable size and startup time), in which case we're abou
On Thursday 12 May 2005 04:58, Patrick R. Michaud wrote:
> On Wed, May 11, 2005 at 09:49:47AM +0200, Jens Rieks wrote:
> > On Wednesday 11 May 2005 04:30, Patrick R. Michaud wrote:
> > > ...well, in looking at it some more it's reasonable until I see
> > > that returning -1 is the way the other fin
On 5/12/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Jerry Gay <[EMAIL PROTECTED]> wrote:
>
> > i'm converting many of the remaining internal_exception() calls to
> > real_exception() (except unimplemented ops, and other valid internal
> > exceptions)
>
> Fine, thanks - applied.
>
> Just cur
I have a couple of questions regarding C< :: > in perl 6 rules.
First, a question of verification -- in
$rule = rx :w / plane :: (\d+) | train :: (\w+) | auto :: (\S+) / ;
"travel by plane jet train tgv today" ~~ $rule
I think the match should fail outright, as opposed to matching "train
[My reply below likely belongs on either perl6-compiler or perl6-language,
but I didn't want to do a lot of cross-posting, so I'm replying
to perl6-internals for now (with apologies to p6i) and followups
should probably go to p6c or p6l. --Pm]
On Thu, May 12, 2005 at 01:51:04AM -0400, Dino Morel
Autrijus Tang wrote:
pugs> split /(..)*/, 1234567890
('', '12', '34', '56', '78', '90')
Is this sane?
Why the empty string match at the start?
--
$TSa == all( none( @Larry ), one( @p6l ))
On Thu, May 12, 2005 at 04:53:06PM +0200, "TSa (Thomas Sandlaï)" wrote:
> Autrijus Tang wrote:
> >pugs> split /(..)*/, 1234567890
> >('', '12', '34', '56', '78', '90')
> >
> >Is this sane?
>
> Why the empty string match at the start?
I don't know, I didn't invent that! :-)
$ perl -le
Autrijus Tang wrote:
I don't know, I didn't invent that! :-)
$ perl -le 'print join ",", split /(..)/, 123'
,12,3
Hmm,
perl -le 'print join ",", split /(..)/, 112233445566'
,11,,22,,33,,44,,55,,66
For longer strings it makes every other match an empt string.
With the "Positions between char
On May 12, 2005, at 11:59 AM, Autrijus Tang wrote:
On Thu, May 12, 2005 at 04:53:06PM +0200, "TSa (Thomas Sandlaï)"
wrote:
Autrijus Tang wrote:
pugs> split /(..)*/, 1234567890
('', '12', '34', '56', '78', '90')
Is this sane?
Why the empty string match at the start?
I don't know, I didn't in
Leopold Toetsch wrote:
parrot -j ord 1.10 user 1.26 real # opt. build rev 8072
and another 20% by inlining the fast path of the array get (set_i_p_ki)
0.91 user 1.09 real # opt build rev 8076
Now its your turn to process files blockwise ;-)
leo
My take, based on S05:
On Thu, 2005-05-12 at 10:33, Patrick R. Michaud wrote:
> I have a couple of questions regarding C< :: > in perl 6 rules.
> First, a question of verification -- in
>
> $rule = rx :w / plane :: (\d+) | train :: (\w+) | auto :: (\S+) / ;
>
> "travel by plane jet train
On Thu, 2005-05-12 at 12:22, David Storrs wrote:
> On May 12, 2005, at 11:59 AM, Autrijus Tang wrote:
> > On Thu, May 12, 2005 at 04:53:06PM +0200, "TSa (Thomas Sandlaï)"
> > wrote:
> >> Autrijus Tang wrote:
> >>
> >>>pugs> split /(..)*/, 1234567890
> >>>('', '12', '34', '56', '78', '90')
On Thu, May 12, 2005 at 06:29:49PM +0200, "TSa (Thomas Sandlaß)" wrote:
> Autrijus Tang wrote:
> >I don't know, I didn't invent that! :-)
> >
> >$ perl -le 'print join ",", split /(..)/, 123'
> >,12,3
>
> Hmm,
>
> perl -le 'print join ",", split /(..)/, 112233445566'
> ,11,,22,,33,,44,,55
> "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
JSD> To bring this back to perl6, autrijus' original query was regarding
JSD> $ pugs -e 'say join ",", split /(..)*/, 1234567890'
JSD> which currently generates a list of ('','12','34','56','78','90')
JSD> In perl5 it would
There's a huge rule at http://juerd.nl/bigrule.txt
Why it was created and what it is for is irrelevant. It's hard to
explain.
Any attempt of using it takes very long (Perl 5 executes the equivalent
thousands of times per second), and eventually segfaults.
An example of a matching word is "chins"
Fresh (and first) checkout and build of parrot (#8075)
on a Mac running OSX 10.3 using the default perl v5.8.1-RC3 built for
darwin-thread-multi-2level.
Failed two tests. Are these known problems or should I dig deeper?
Tim.
t/pmc/config...NOK 2# Failed test (t/pmc/config.t a
[EMAIL PROTECTED] wrote:
> Leopold Toetsch wrote:
>
> > parrot -j ord 1.10 user 1.26 real # opt. build rev 8072
>
> and another 20% by inlining the fast path of the array get (set_i_p_ki)
>
> 0.91 user 1.09 real # opt build rev 8076
I've written some files to go into ex
On Thu, May 12, 2005 at 06:29:49PM +0200, "TSa (Thomas Sandla?)" wrote:
> perl -le 'print join ",", split /(..)/, 112233445566'
> ,11,,22,,33,,44,,55,,66
[snipped]
> perl -le 'print join ",", split /(..)/, 11223'
> ,11,,22,3
>
> Am I the only one who finds that inconsistent?
Maybe, but it's becau
On Thu, May 12, 2005 at 12:53:46PM -0400, Aaron Sherman wrote:
> On Thu, 2005-05-12 at 10:33, Patrick R. Michaud wrote:
> > Next on my list, S05 says "It is illegal to use :: outside of
> > an alternation", but A05 has
> >
> > /[:w::foo bar]/
>
> I can't even figure out what that means. :w t
On Thu, May 12, 2005 at 12:53:46PM -0400, Aaron Sherman wrote:
> My take, based on S05:
>
> > In other words, it acts as though one had written
> >
> > $rule = rx :w / plane ::: (\d+) | train ::: (\w+) | auto ::: (\S+) / ;
> >
> > and not
> >
> > $rule = rx :w /[ plane :: (\d+) | tr
On Thu, May 12, 2005 at 12:33:59PM -0500, Jonathan Scott Duff wrote:
>
> > > /[:w\bfoo bar]/# not exactly the same as above
> >
> > No, I think that's exactly the same.
>
> What does \b mean again? I assume it's no longer backspace?
For as long as I can remember \b has meant "word boun
On Thu, May 12, 2005 at 12:48:16PM -0500, Patrick R. Michaud wrote:
> On Thu, May 12, 2005 at 12:33:59PM -0500, Jonathan Scott Duff wrote:
> >
> > > > /[:w\bfoo bar]/# not exactly the same as above
> > >
> > > No, I think that's exactly the same.
> >
> > What does \b mean again? I assum
On Thu, May 12, 2005 at 01:12:26PM -0400, Uri Guttman wrote:
> > "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
>
> JSD> To bring this back to perl6, autrijus' original query was regarding
>
> JSD>$ pugs -e 'say join ",", split /(..)*/, 1234567890'
>
> JSD> which curr
> "PRM" == Patrick R Michaud <[EMAIL PROTECTED]> writes:
PRM> On Thu, May 12, 2005 at 12:33:59PM -0500, Jonathan Scott Duff wrote:
>>
>> > > /[:w\bfoo bar]/# not exactly the same as above
>> >
>> > No, I think that's exactly the same.
>>
>> What does \b mean again? I
On Thu, May 12, 2005 at 06:45:18PM +0200, Juerd wrote:
> There's a huge rule at http://juerd.nl/bigrule.txt
>
> Why it was created and what it is for is irrelevant. It's hard to
> explain.
>
> Any attempt of using it takes very long (Perl 5 executes the equivalent
> thousands of times per second)
On behalf of the Pugs team, I am delighted to announce the release
of Pugs 6.2.3, with Parrot embedding, Perl 6 Rules support (via PGE),
an initial sketch of OO system. Multi-thread programming with
async/kill/join/detach is now supported as well.
Also of note are many new, working modules under
On Thu, 2005-05-12 at 13:44, Patrick R. Michaud wrote:
> On Thu, May 12, 2005 at 12:53:46PM -0400, Aaron Sherman wrote:
> > > In other words, it acts as though one had written
> > >
> > > $rule = rx :w / plane ::: (\d+) | train ::: (\w+) | auto ::: (\S+) / ;
> > >
> > > and not
> > >
>
While E02 states that "is chomped" sets the chomped property of
afilehandle, I didn't find any detailed specifications in any of the
As or Ss.
So - is "is chomped" always the equivalent of:
while ( ) {
chomp;
}
For instance - you have opened the file rw
Or, the idea of having mutator and n
On Thu, May 12, 2005 at 12:03:55PM -0500, Jonathan Scott Duff wrote:
: I think that the above split should generate a list like this:
:
: ('', [ '12','34','56','78','90'])
Yes, though I would think of it more generally as
('', $0, '', $0, '', $0, ...)
where in this case it just happen
It looks like I'm going to have to punt on finishing S29.
I'm finding myself in a perpetual state of either no time to work on it,
or when there is time, having insufficient brain power left to properly
assimilate everything that needs to be considered to do any of the
functions justice. Looking
Thit has led to surprising results in Pugs's Net::IRC:
if 'localhost:80' ~~ /^(.+)\:(\d+)$/ {
my $socket = connect($0, $1);
}
If $1 is a match object here, and connect() assumes Int on its second
argument, then it will connect to port 1, as the match object numifies
to 1 (indicati
$rule = rx :w / plane ::: (\d+) | train ::: (\w+) | auto ::: (\S+) / ;
$rule = rx :w /[ plane :: (\d+) | train :: (\w+) | auto :: (\S+) ]/ ;
On Thu, May 12, 2005 at 02:29:24PM -0400, Aaron Sherman wrote:
> On Thu, 2005-05-12 at 13:44, Patrick R. Michaud wrote:
> > On Thu, May 12, 2005 at 1
Hi,
I've just uploaded the new Pugs Live CD, version 6.2.3, r3112.
You can find it at
http://linide.sf.net/pugs-livecd-6.2.3.iso (3.9 MiB)
Or you can compile the cd on your own by checking out a copy of Pugs and
then executing (currently on Linux only)
$ cd util/livecd
$ ./mklivecd.pl
The
Hello,
In the current SVN repository are 76 .cvsignore files. In SVN they aren't used
any more. SVN uses the property 'svn:ignore' on a directory instead.
During the cvs => svn transition the svn:ignore properties were set but in
the recent weeks they started to diverge. Currently (r8078) 22 .cv
[EMAIL PROTECTED] wrote:
I've written some files to go into examples/benchmark which time the
raw throughput of the md5 part, which excluding the load/compile
phases.
That's not really needed. Startup time is almost nothing with file sizes
bigger then some MB. And below that, you don't get reasona
On Fri, May 13, 2005 at 03:23:20AM +0800, Autrijus Tang wrote:
> Is it really intended that we get into habit of writing this?
>
> if 'localhost:80' ~~ /^(.+)\:(\d+)$/ {
> my $socket = connect(~$0, +$1);
> }
>
> It looks... weird. :)
And it would have to be
if 'localhost:80'
On Thu, May 12, 2005 at 12:01:59PM -0700, Larry Wall wrote:
> On Thu, May 12, 2005 at 12:03:55PM -0500, Jonathan Scott Duff wrote:
> : I think that the above split should generate a list like this:
> :
> : ('', [ '12','34','56','78','90'])
>
> Yes, though I would think of it more generally as
On Thu, May 12, 2005 at 02:56:37PM -0500, Jonathan Scott Duff wrote:
> On Thu, May 12, 2005 at 12:01:59PM -0700, Larry Wall wrote:
> > Yes, though I would think of it more generally as
> >
> > ('', $0, '', $0, '', $0, ...)
> >
> > where in this case it just happens to be
> >
> > ('', $0)
sub foo { my $x; BEGIN { $x = 3 }; say $x }
foo; foo; foo;
Currently in perl5 and pugs this prints "3\n\n\n".
Should BEGIN blocks be able to modify values in lexical variables that
don't really exist yet? (People can use state after all to get a
variable which does exist early enough for them
Tim wrote:
Fresh (and first) checkout and build of parrot (#8075)
first???\ :-)
Failed TestStat Wstat Total Fail Failed List of Failed
---
t/dynclass/pyint.t1 256261 3.85% 26
This test shoul
On Thu, 2005-05-12 at 15:41, Patrick R. Michaud wrote:
> $rule = rx :w / plane ::: (\d+) | train ::: (\w+) | auto ::: (\S+) / ;
> $rule = rx :w /[ plane :: (\d+) | train :: (\w+) | auto :: (\S+) ]/ ;
>
> On Thu, May 12, 2005 at 02:29:24PM -0400, Aaron Sherman wrote:
> > On Thu, 2005-05-12
On Thu, May 12, 2005 at 09:06:48PM +0100, Benjamin Smith wrote:
> sub foo { my $x; BEGIN { $x = 3 }; say $x }
> foo; foo; foo;
>
> Currently in perl5 and pugs this prints "3\n\n\n".
>
> Should BEGIN blocks be able to modify values in lexical variables that
> don't really exist yet? (People ca
Ryan King finally submitted to me a full patch to add the description to
Test::Builder diagnostic output. Unfortunately I'm not hot on his
formatting, however it has finally kicked my ass into examining the problem.
Just to refresh everyone, this is what the output of
#!/usr/bin/perl -w
use Te
Michael G Schwern wrote:
Ryan King finally submitted to me a full patch to add the description to
Test::Builder diagnostic output. Unfortunately I'm not hot on his
formatting, however it has finally kicked my ass into examining the problem.
Just to refresh everyone, this is what the output of
#!
On Thu, May 12, 2005 at 06:45:12PM -0400, Randy W. Sims wrote:
> It's worded as if the description were a name rather than a description.
No matter what TAP wants to call it, its just more information associated
with the test. This might be a name, a description, an explaination,
diagnostic inf
Leopold Toetsch wrote:
[EMAIL PROTECTED] wrote:
I've written some files to go into examples/benchmark which time the
raw throughput of the md5 part, which excluding the load/compile
phases.
That's not really needed. Startup time is almost nothing with file
sizes bigger then some MB. And below tha
Rod Adams wrote:
It looks like I'm going to have to punt on finishing S29.
On behalf of pugs committers, we will gladly adopt this task, which is in
the pugs repository already at docs/S29draft.pod, as well as having a set
of foundation classes that correspond to all these object methods in
docs/sr
On Thu, May 12, 2005 at 05:15:55PM -0400, Aaron Sherman wrote:
> On Thu, 2005-05-12 at 15:41, Patrick R. Michaud wrote:
> > False. In the first case the group is the whole rule. In the second
> > case the group would not include the (implied) '.*?' at the start of
> > the rule.
>
> This was a ve
On Fri, May 13, 2005 at 04:05:23AM +0800, Autrijus Tang wrote:
> > On Thu, May 12, 2005 at 12:01:59PM -0700, Larry Wall wrote:
> > > Yes, though I would think of it more generally as
> > >
> > > ('', $0, '', $0, '', $0, ...)
> > >
> > > where in this case it just happens to be
> > >
> > >
On Fri, 2005-05-13 at 12:07 +1200, Sam Vilain wrote:
> Rod Adams wrote:
> > It looks like I'm going to have to punt on finishing S29.
>
> On behalf of pugs committers, we will gladly adopt this task, which is in
> the pugs repository already at docs/S29draft.pod, as well as having a set
> of found
On Thu, May 12, 2005 at 08:33:40PM -0400, Rick Delaney wrote:
> On Fri, May 13, 2005 at 04:05:23AM +0800, Autrijus Tang wrote:
> > pugs> map { ref $_ } split /(..)*/, 1234567890
> > (::Str, ::Array::Const)
>
> Sorry if I'm getting ahead of the implementation but if it is returning
> $0 the
On Thu, May 12, 2005 at 08:33:40PM -0400, Rick Delaney wrote:
> Sorry if I'm getting ahead of the implementation but if it is returning
> $0 then shouldn't ref($0) return ::Rule::Result or somesuch? It would
> just look like an ::Array::Const if you treat it as such.
...also note that the $0 here
On Thu, May 12, 2005 at 06:45:12PM -0400, Randy W. Sims ([EMAIL PROTECTED])
wrote:
> >Ryan King finally submitted to me a full patch to add the description to
> >Test::Builder diagnostic output. Unfortunately I'm not hot on his
> >formatting, however it has finally kicked my ass into examining t
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Thu, 12 May 2005 09:19:00 +0200
Bob Rogers wrote:
>
> I'm sorry, but I'm still seeing the same syndrome in r8070, segfaulting
> in the same place, though now for only a subset of *.pbc files . . .
Yet another uninitialized poin
Can this be right ? I checked out DBD-mysql-2.9007 and ran it through
Devel::Cover. Apart from skipping 15 tests to do with leaks and 1 test
to do with transactions, the overall coverage figure from Devel::Cover
is 56%
All tests successful, 1 test and 14 subtests skipped.
Files=18, Tests=769, 1
On Fri, May 13, 2005 at 12:18:04PM +1000, [EMAIL PROTECTED] wrote:
> Can this be right ? I checked out DBD-mysql-2.9007 and ran it through
> Devel::Cover. Apart from skipping 15 tests to do with leaks and 1 test
> to do with transactions, the overall coverage figure from Devel::Cover
> is 56%
Leif Eriksen wrote:
Can this be right ? I checked out DBD-mysql-2.9007 and ran it through
Devel::Cover. Apart from skipping 15 tests to do with leaks and 1 test
to do with transactions, the overall coverage figure from Devel::Cover
is 56%
All tests successful, 1 test and 14 subtests skipped.
Fi
On Thu, May 12, 2005 at 02:55:36PM -0500, Patrick R. Michaud wrote:
> On Fri, May 13, 2005 at 03:23:20AM +0800, Autrijus Tang wrote:
> > Is it really intended that we get into habit of writing this?
> >
> > if 'localhost:80' ~~ /^(.+)\:(\d+)$/ {
> > my $socket = connect(~$0, +$1);
> >
On 5/12/05, Jonathan Scott Duff <[EMAIL PROTECTED]> wrote:
> On Thu, May 12, 2005 at 02:55:36PM -0500, Patrick R. Michaud wrote:
> > On Fri, May 13, 2005 at 03:23:20AM +0800, Autrijus Tang wrote:
> > > Is it really intended that we get into habit of writing this?
> > >
> > > if 'localhost:80' ~
On Thu, May 12, 2005 at 02:55:36PM -0500, Patrick R. Michaud wrote:
: On Fri, May 13, 2005 at 03:23:20AM +0800, Autrijus Tang wrote:
: > Is it really intended that we get into habit of writing this?
: >
: > if 'localhost:80' ~~ /^(.+)\:(\d+)$/ {
: > my $socket = connect(~$0, +$1);
: >
[EMAIL PROTECTED] wrote:
Leif Eriksen wrote:
Can this be right ?
--- -- -- -- --
-- --
File stmt branch condsub
time total
--- -- -- -- --
-- -
Larry Wall wrote:
I think we already said something like that once some number of
months ago. +$1 simply has to be the numeric value of the match.
Agreed.
Anyway, while we could have
a method for the .matchcount, +$1[] should work fine too.
Yep.
Actually, it's not clear to me offhand why @1 sho
On Thu, May 12, 2005 at 02:52:01PM -0400, Joshua Gatcomb wrote:
: While E02 states that "is chomped" sets the chomped property of
: afilehandle, I didn't find any detailed specifications in any of the
: As or Ss.
:
: So - is "is chomped" always the equivalent of:
:
: while ( ) {
: chomp;
: }
On Fri, May 13, 2005 at 02:00:10PM +1000, Damian Conway wrote:
: >Actually, it's not clear to me offhand why @1 shouldn't mean $1[]
: >and %1 shouldn't mean $1{}.
:
: It *does*. According to the recent capture semantics document:
:
:> Note that, outside a rule, C<@1> is simply a shorthand for
On Thu, May 12, 2005 at 09:33:37AM -0500, Patrick R. Michaud wrote:
: Also, A05 proposes incorrect alternatives to the above
:
: /[:w[]foo bar]/# null pattern illegal, use
: /[:w()foo bar]/# null capture illegal, and probably undesirable
: /[:w\bfoo bar]/# not exactly the
On Fri, May 13, 2005 at 01:27:41PM +1000, [EMAIL PROTECTED] wrote:
> OK, but if we remove that, the Stmt goes to ~70% wich is still
> shockingly low for such an important module. It is also very distressing
> that the Sub column isnt at 100% - why you would go to the effort of
> writing test ca
On Thu, May 12, 2005 at 08:56:39PM -0700, Larry Wall wrote:
> On Thu, May 12, 2005 at 09:33:37AM -0500, Patrick R. Michaud wrote:
> : Also, A05 proposes incorrect alternatives to the above
> :
> : /[:w[]foo bar]/# null pattern illegal, use
> : /[:w()foo bar]/# null capture illega
On Wed, May 11, 2005 at 08:00:20PM -0500, Patrick R. Michaud wrote:
: Somehow I'd like to get rid of those inner angles, so
: that we always use <+alpha>, <+digit>, <-sp>, <-punct> to
: indicate named character classes, and specify combinations
: with constructions like <+alpha+punct-[aeiou]>
On Thu, May 12, 2005 at 08:10:42PM -0700, Larry Wall wrote:
> On Thu, May 12, 2005 at 02:55:36PM -0500, Patrick R. Michaud wrote:
> : My suggestion is that a match object in numeric context is the
> : same as evaluating its string value in a numeric context. If
> : we need a way to find out the nu
On Thu, May 12, 2005 at 08:10:42PM -0700, Larry Wall wrote:
> On Thu, May 12, 2005 at 02:55:36PM -0500, Patrick R. Michaud wrote:
> : On Fri, May 13, 2005 at 03:23:20AM +0800, Autrijus Tang wrote:
> : > Is it really intended that we get into habit of writing this?
> : >
> : > if 'localhost:80'
[EMAIL PROTECTED] wrote:
I hope you're not just now realizing
that some of the most important and popular modules are also the most
undertested?
I always knew they would be less than perfect, I just had no idea the 2nd
most popular would be this bad.
Anyway, I've booked a weekend at the neares
Patrick surmised:
So I'm guessing that we're all in agreement that +$/, +$1, and
+$ all refer to the numeric value of the string matched,
as opposed to what's currently written about their values in the
draft...?
Yes. The semantics proposed in the draft have proved to be too orthogonal for
prac
77 matches
Mail list logo
