RE: Split with negative limits, and other weirdnesses

Hmmm, my understanding was that it stopped *splitting* after the limit, but it doesn't stop "consuming" the source; rather the entire remainder is returned as the last item in the list, even if it contains the delimiter. A bit like this: sub split($pat, $src, $limit) { @

[perl #43851] [CAGE] All calls to stack_entry need to be NULL-checked

On Fr. 13. Jul. 2007, 16:21:54, rgrjr wrote: > Are there any? The only ones I can find that that Splint might be > complaining about are the derefs in rotate_entries, but the code > explicitly checks that stack_height is large enough such that > stack_entry will never return NULL. True? Looks l

Re: Recommended Perl 6 best practices?

On Tue, 30 Sep 2008, Patrick R. Michaud wrote: > Just for pedantic clarity, what C< $directive ne 'VAR' & 'LOOP' & 'IF' > > really gives is > > all( $directive ne 'VAR', $directive ne 'LOOP', $directive ne 'IF' ) > > In other words, the result of the expression is an all() Junction. In > boole

Re: [perl #59112] Failing test in t/examples/library.t

James (>): > Let's start with an elementary question: What does Configure.pl say for > you at this step: > > auto::pcre - Does your platform support pcre auto::pcre - Does your platform support pcreyes, 7.7. // Carl

[perl #59484] [TODO] Implement $?PACKAGE in Rakudo

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #59484] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59484 > ...as described in S02: Package declara

[perl #46083] [TODO] Fix memory leak in src/pmc/parrotio.pmc:open()

Fixed in r31508

[perl #59480] [TODO] Refactor Str.chop

# New Ticket Created by Vasily Chekalkin # Please include the string: [perl #59480] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59480 > Hello. There is suggestion from Pm for Str.chop > > +.sub 'chop' :method > > +

[perl #46667] [TODO] [C] Do we need properties in the default object system?

> This check can be removed from default.pmc. Property values should not > be returned by get_attr_str. Done in r31509

[perl #57690] [BUG] make headerizer breaks build

On Mar. Ago. 12 15:05:57 2008, Whiteknight wrote: > This probably isn't headerizer's fault, it's more likely the fault of > IMCC for being so damn complicated. We could change all the function > definitions in the IMCC related files to use "struct _IMC_Unit" instead > of "IMC_Unit" which would res

[perl #59476] [TODO] Refactor Str.capitalize.

# New Ticket Created by Vasily Chekalkin # Please include the string: [perl #59476] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59476 > Hello. There is suggestion from Pm for Str.capitalize > + > > +=item capitalize

[perl #59472] [TODO] Randomize hash seed

# New Ticket Created by Bernhard Schmalhofer # Please include the string: [perl #59472] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59472 > In src/hash.c:816 there is a TODO comment: /* TODO randomize */ hash->see

Re: [perl #59398] [PATCH] Moving methods from Str.pir toany-str.pir

Patrick R. Michaud wrote: Yes, please. And these are cleanups that someone should be able to do with only a modest knowledge of PIR (and perhaps a good chance to learn PIR :-). Done. #59486 and #59490 -- Bacek

[perl #59410] [PATCH] CONTROL_LOOP_NEXT support for pct. Rakudo won't build, though. -- callgrind output

Attached is callgrind output from trying to compile rakudo with this patch. As you can see, the most-called functions by far are: /home/sweeks/src/parrot/compilers/imcc/sets.c:set_add /home/sweeks/src/parrot/compilers/imcc/cfg.c:compute_dominance_frontiers

Re: Recommended Perl 6 best practices?

On Tue, Sep 30, 2008 at 02:31:46PM +1000, Jacinta Richardson wrote: > Carl Mäsak wrote: > > The "correct" form using junctions would be this: > > > > die "Unrecognized directive: TMPL_$directive" > >if $directive ne 'VAR' & 'LOOP' & 'IF'; > > which makes sense, because this does give us: > >

Re: Dumb questions about array slicing...

Good point on the other special subscript values. The PIR as currently being generated couldn't work anyway, since the subscript is being put in an Int register instead of a PMC one. On 9/30/08, Moritz Lenz <[EMAIL PROTECTED]> wrote: > Mark J. Reed wrote: >> I didn't see anything in the issue t

Re: Dumb questions about array slicing...

Mark J. Reed wrote: > I didn't see anything in the issue tracker, nor did any tests fail, There are failing (but TODOed) tests somewhere below t/spec/S02-builtin_data_types/ > but am I correct in assuming that array slicing is simply not > implemented yet in Rakudo? Correct. > $ ./perl6 -e 'my