On Jul 28, 2010, at 1:27 PM, Mark J. Reed wrote:
> On Wednesday, July 28, 2010, Jon Lang wrote:
>> Keep it simple, folks! There are enough corner cases in Perl 6 as
>> things stand; we don't need to be introducing more of them if we can
>> help it.
>
> Can I get an Amen? Amen!
> --
> Mark J.
On Jul 28, 2010, at 1:37 PM, Mark J. Reed wrote:
> On Wed, Jul 28, 2010 at 2:30 PM, Chris Fields wrote:
>> On Jul 28, 2010, at 1:27 PM, Mark J. Reed wrote:
>>> Can I get an Amen? Amen!
>>> --
>>> Mark J. Reed
>>
>> +1. I'm agnosti
Moritz,
Funny, went to IRC after seeing this brought up to respond, and didn't even
notice you made this the weekly contribution to perl6! I have a Str.trans
implementation on my rakudo github fork that's working and passes 20 tests:
http://github.com/cjfields/rakudo
A few caveats:
1) It'
Would you want to use something else for that, maybe .comb?
From the spec:
'The comb function looks through a string for the interesting bits, ignoring
the parts that don't match. In other words, it's a version of split where you
specify what you want, not what you don't want.'
chris
On Jan 2
On Jun 2, 2009, at 5:11 PM, Daniel Carrera wrote:
John M. Dlugosz wrote:
So CPAN6 is basically only going to be for Parrot?
What are you talking about? Did you even read my email? I said that
a module might be implemented in multiple languages (see Digest::SHA
VS Digest::SHA::PurePerl) an
On Feb 11, 2009, at 2:46 PM, Carl Mäsak wrote:
Jon (>), Jonasthan (>>):
If we declared, for example:
role A::B {};
Then what should a reference to A be here? At the moment, Rakudo
treats it
as a post-declared listop, however I suspect we should be doing
something a
bit smarter? If so, w
On Jul 18, 2008, at 5:18 PM, Jonathan Worthington wrote:
Hi,
Chris Fields wrote:
The PGE::Match appears to be converted to a Str, regardless of the
invoking object type. The following is .match (in any-str.pir,
with the builtins). Also, .ACCEPTS now uses .match to retrieve the
Match
On Jul 17, 2008, at 9:41 PM, Patrick R. Michaud wrote:
On Thu, Jul 17, 2008 at 02:20:33PM -0500, Chris Fields wrote:
Okay, I'll set it up so "$foo = 'abcd'.match(/+/)" returns a
Match object, and $/ would remain unset. Makes sense to me.
Right now the match object i
On Jul 17, 2008, at 1:56 AM, Moritz Lenz wrote:
Essentially the difference is that smart-match sets $/, while
a simple call to .match probably should not.
Pm
I can have .match not set $/ for now and simply return matches based
on context
IMHO that's the wrong approach. Perl 6 tries not to
On Jul 16, 2008, at 5:45 PM, Chris Fields wrote:
On Jul 16, 2008, at 1:28 PM, Patrick R. Michaud wrote:
On Wed, Jul 16, 2008 at 11:20:28AM -0500, Chris Fields wrote:
I have submitted a simple 'match' implementation for rakudo (method
version of m//, RT#56970) and ran into an
On Jul 16, 2008, at 1:28 PM, Patrick R. Michaud wrote:
On Wed, Jul 16, 2008 at 11:20:28AM -0500, Chris Fields wrote:
I have submitted a simple 'match' implementation for rakudo (method
version of m//, RT#56970) and ran into an odd issue. The current
version of match which works u
I have submitted a simple 'match' implementation for rakudo (method
version of m//, RT#56970) and ran into an odd issue. The current
version of match which works uses a tail call:
.sub 'match' :method
.param pmc x
.return x.ACCEPTS(self)
.end
If I try the following:
.sub 'match' :m
I am working on the transliteration method operator (trans()) for
Rakudo and wanted to get some input on how character ranges are to be
used.
Should spaces be ignored in ranges like 'A .. Z'? Currently the
implementation I have ignores those spaces but counts any other spaces
as importan
I am working on the transliteration method operator (trans()) for
Rakudo and wanted to get some input on how character ranges are to be
used.
Should spaces be ignored in ranges like 'A .. Z'? Currently the
implementation I have ignores those spaces but counts any other spaces
as importan
That also fixes the bus error I reported in rt:
http://rt.perl.org/rt3/Public/Bug/Display.html?id=54004
I went ahead and closed that ticket out. jonathan++
Thanks!
chris
On May 16, 2008, at 7:01 AM, Jonathan Worthington wrote:
Chris Fields wrote:
There appears to be a possible GC-related
There appears to be a possible GC-related bug introduced to Parrot
prior to r27449 which is showing up in Rakudo. Using the following
script (courtesy of Jonathan W):
class Foo {
has $.x;
method boo { say $.x }
}
class Bar is Foo {
method set($v) {
16 matches
Mail list logo
