# New Ticket Created by Moritz Lenz
# Please include the string: [perl #67050]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67050 >
13:52 < zulon> rakudo: say "3".Num
13:52 < p6eval> rakudo d95def: OUTPUT«Method 'Num' not
I thought unary + was scalar/item? context in perl6, not numify.
--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com
system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu
electrical and computer engineering, carnegie mellon universityKF8NH
PGP.si
On Tue Nov 18 08:07:50 2008, mor...@casella.faui2k3.org wrote:
> Rakudo needs to have the 'is rw' trait on classes at some point (which
> according to S12 implies that all attributes are rw by default).
>
After some changes yesterday, we now implement this and pass all of the
tests in S12-class/rw
# New Ticket Created by Daniel Ruoso
# Please include the string: [perl #67064]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67064 >
rakudo: say [~] [] xx 3
rakudo 1831bd: OUTPUT«a b ca b ca b c»
rakudo: say [X] [] xx
On Thu Apr 02 06:26:38 2009, masak wrote:
> rakudo: class A { has $.foo; submethod BUILD($obj) { $!foo = 7
> } }; say A.new.foo;
> rakudo c40f3b: OUTPUT«Null PMC access in getprop() [...]
> * masak submits rakudobug
Thanks to some fixes a little while back, this now works:
<@jnthn> rakudo: clas
On Mon Mar 02 01:03:30 2009, ml...@physik.uni-wuerzburg.de wrote:
>
> Rakudo 08b789048:
> ./perl6 -e 'class A { submethod BUILD(*...@a) { say @a.perl } }; A.new(x
=> 3)'
> Could not locate a method 'perl' to invoke on class 'A'.
>
> Now that's bad. BUILD shouldn't receive the initially created ob
On Tue, Jun 30, 2009 at 4:55 AM, Brandon S. Allbery
KF8NH wrote:
> I thought unary + was scalar/item? context in perl6, not numify.
+ is numeric context - which is one of several subtypes of item
context. Generic item context is item(); + numifies; ? boolifies; ~
stringifies.
I'm guessing you
On Mon Jun 29 13:45:16 2009, druoso wrote:
> rakudo: say [~] [] xx 3
> rakudo 1831bd: OUTPUT«a b ca b ca b c»
> rakudo: say [X] [] xx 3
> rakudo 1831bd: OUTPUT«Statement not terminated properly at line
> 2, near "[] "in Main (src/gen_setting.pm:3257)»
> std: say [X] [] xx 3
> std 27309: OU
On Mon Jun 22 06:38:06 2009, masak wrote:
> std: subset A of Int;
> std 27169: OUTPUT«ok 00:02 35m»
> rakudo: subset A of Int;
> rakudo 1b06df: OUTPUT«Statement not terminated properly at
> line 2 [...]
> * masak submits rakudobug
Now works in git 1831bd1. Unfudged the test from kyle++ that c
# New Ticket Created by "Kyle Hasselbacher"
# Please include the string: [perl #67058]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67058 >
I discovered this while trying to write a test for another bug report.
Here's th
On Fri Mar 13 05:23:29 2009, masak wrote:
> std: sub foo(1,2,3) {...}
> std 25816: OUTPUT«ok 00:02 35m»
> Heh
> jnthn, is that already known?
> I didn't even know that was valid syntax... :-P
However, it is valid syntax, and pretty cool syntax at that. It's also
supported in Rakudo as of git
Oops, forgot to cc this to the list...
On Tue Jun 30 05:30:14 2009, jn...@jnthn.net wrote:
> On Thu May 28 11:52:22 2009, pmichaud wrote:
> > See S12:611:
> >
> > "If you attempt to get around this by declaring C as
> > a method rather than a submethod, that will also be flagged as a
dire
On Sun Apr 19 10:11:22 2009, cosmicnetworks wrote:
> Please find the patch attached. Let me know if you have any questions.
>
> I've tested this code against the chdir and cwd spec tests.
>
I fixed a nit in the $*CWD implementation and applied that one. The test
file all passed, so added that t
On Mon Jun 29 00:36:42 2009, fernandocor...@gmail.com wrote:
> implemented:
> - "not" "Object"'s method
> - "sign" "Num"'s method
>
> Thats my first time to send a patch, I don't know if its OK, but I really
> want to help.
Thank you for the patches! However, they may need some refactoring (or
Now fixed in e0a9d86, and we now have several operators being defined in
the setting (along with tests using those operators).
Closing ticket, thanks!
Pm
On Wed Jun 24 12:05:29 2009, masak wrote:
> rakudo: say &infix:<+>
> rakudo 0e0671: OUTPUT«10»
> why is this giving 10 with no args?
> oh
> that's... rubbish, I'd say
> * masak submits rakudobug
As of git 466baf6 it gives the more sensible:
> say &infix:<+>
infix:+
Though infix:<+> would p
On Sat Jun 20 12:15:49 2009, pmichaud wrote:
> The following code demonstrates that MultiSub and Perl6MultiSub
> do not stringify to a reasonable name.
>
> for 1.^methods {
> say ">$_< {$_.PARROT}";
> }
>
Fixed these in git 466baf6, plus added a test for multi-sub
stringificati
On Tue Jun 30 01:56:39 2009, allb...@ece.cmu.edu wrote:
> I thought unary + was scalar/item? context in perl6, not numify.
When in doubt, check the spec. :)
S03 (]):
] Unlike in Perl 5, where + is a no-op, this operator coerces to
] numeric context in Perl 6.
So prefix:<~> stringifies, prefix:<+
Rakudo 95a2c4f now gives a more useful error message when returning the
failure for not finding a given substring:
pmich...@orange:~/rakudo$ ./perl6
> say index "abcd", "x"
Substring 'x' not found in 'abcd'
Closing ticket, thanks!
Pm
On Sun Jun 28 12:05:28 2009, moritz wrote:
> 20:11 <@moritz_> rakudo: sub a { state $x //= 3; $x++; say $x }; a(); a()
> 20:12 < p6eval> rakudo 6c43f9: OUTPUT«44»
>
> Although that's better written as 'state $x = 3', it should IMHO give
> the result 4\n5\n, not 4\n4\n
>
Aye, agree. And after gi
The infix: operator has now been added in Rakudo a4978b9, with a
test added to t/spec/S03-operator/misc.t in r27322.
Closing ticket,
Pm
On Mon Jun 29 10:34:57 2009, KyleHa wrote:
> I discovered this while trying to write a test for another bug report.
> Here's the minimal test, which I'll put in
> pugs/t/spec/S04-declarations/state-rtX.t once I get a number back
> from this bug report.
>
The bug is fixed and that test now pas
Author: lwall
Date: 2009-06-30 18:14:08 +0200 (Tue, 30 Jun 2009)
New Revision: 27324
Modified:
docs/Perl6/Spec/S11-modules.pod
Log:
[S11] attempt to break down use/require further for ELISHEVA++
Modified: docs/Perl6/Spec/S11-modules.pod
Patrick R. Michaud via RT wrote:
> On Fri Jun 26 07:56:40 2009, masak wrote:
>> rakudo: my $a = :x[]
>> rakudo 6c43f9: OUTPUT«Null PMC access in find_method() [...]
>> * masak submits rakuodbug
>> rakudo: :x[]
>> rakudo 6c43f9: OUTPUT«Null PMC access in find_method() [...]
>
>
> What should $
On Sat Apr 11 15:02:06 2009, masak wrote:
> rakudo: class A { has $.cl = { self.say } }; A.new.cl()()
> rakudo 5b679a: OUTPUT«Null PMC access in get_pmc_keyed() [...]
> * masak submits rakudobug 307
Works in latest Rakudo; added test to S12-attributes/instance.t to make
sure it keeps on working.
On Fri Jun 26 07:56:40 2009, masak wrote:
> rakudo: my $a = :x[]
> rakudo 6c43f9: OUTPUT«Null PMC access in find_method() [...]
> * masak submits rakuodbug
> rakudo: :x[]
> rakudo 6c43f9: OUTPUT«Null PMC access in find_method() [...]
What should $a contain in the above case? I.e., what's the
Author: ruoso
Date: 2009-06-30 19:18:24 +0200 (Tue, 30 Jun 2009)
New Revision: 27331
Modified:
docs/Perl6/Spec/S11-modules.pod
Log:
[spec/S11] better to be sorry than not doing. here is my proposed change to the
representation of how a module is loaded
Modified: docs/Perl6/Spec/S11-modules.po
On Fri Jun 26 09:08:56 2009, moritz wrote:
> 18:07 <@moritz_> rakudo: class NotAny is Object { };
> 18:07 < p6eval> rakudo 6c43f9: OUTPUT«Could not build C3 linearization:
> ambiguous hierarchyin Main (/tmp/dXMaaubcDg:2)»
>
Fixed in git aa1a18d and added spectest to S12-class/inh
On Sun Oct 26 12:27:26 2008, masak wrote:
> Rakudo r32151 contains a bug which makes it "read" a nonexistent blank
> line at the end of files.
>
> $ wc README | awk '{ print $1 }'
> 102
>
> $ =$*IN; }; say $l'
> 103
IO.pod:1207 claims that "IO.eof" is gone, to be replaced with
C. But I can't s
Now fixed in ee1fd13:
$ ./perl6
> say &infix:<+>.WHAT
Multi()
Assigning to moritz++ for spectest coverage, if needed.
Pm
I've written a test for this in S12-methods/what.t in r27345.
# RT #66928
{
lives_ok { &infix:<+>.WHAT }, 'Can .WHAT built-in infix op';
isa_ok &infix:<+>.WHAT, Multi, '.WHAT of built-in infix op is Multi';
}
Kyle
On Tue, Jun 30, 2009 at 8:20 PM, Patrick R. Michaud via
RT wrote:
> Now fi
On Tue Jun 30 18:47:59 2009, KyleHa wrote:
> I've written a test for this in S12-methods/what.t in r27345.
Thanks! Closing ticket!
Pm
On Sun Jun 21 23:57:17 2009, amoc wrote:
> : bash$ perl6
> : > 1 ?? 1,2 !! 3,4
> : Ternary error
> : bash$
>
> this is not wrong as infix:<,> has looser precedence than the ternary
> operator( ?? !! )
> but when ternary error occurs, the program emits the error and dies.
>
> should provide the pr
On Sun Jun 21 10:44:43 2009, moritz wrote:
> iterating over $*VM.kv shows more than one key:
>
> $ perl6 -e 'my $keys = 0; for %*VM.kv -> $k, $v { $keys++}; say $keys'
> 141
>
> Somehow the inner hash is flattened. Using a normal hash I couldn't
> reproduce
> this behaviour.
Now fixed in 6c6299f
I've changed this ticket to indicate that it's waiting on spec
clarification as to the exact meaning of in regexes.
Pm
35 matches
Mail list logo