The topic for #perl6 is: pugscode.org/ planetsix.perl.org/ | nopaste: sial.org/pbot/perl6 | pugs: [~] <m oo se> (or rakudo:, kp6:, elf: etc.) (or perl6: for all) | irclog: irc.pugscode.org/
Set by TimToady on 25 November 2008.
pugs_svn r24321 | jnthn++ | [t/spec] todo a test that we don't pass in the rakudoreg branch, but that I'm not sure matches the spec anyway. 00:30
r24322 | jnthn++ | [t/spec] If B is a regex, 'abc' ~~ B is surely not the way to match against it, since that's like B() on the RHS. Change it to &B (we were getting away with this before registering symbols - in the branch of Rakudo that now does this, we stop accidentally passing this test as it 00:34
..was.)
|mjk| when perl6 release? 00:42
pugs_svn r24323 | azawawi++ | [Syntax::Highlight::Perl6] Removed META.yml and Makefile.PL now generates it with 00:48
r24323 | azawawi++ | [Syntax::Highlight::Perl6] with the correct license
pugs_svn r24324 | azawawi++ | [Syntax::Highlight::Perl6] Bumped version to 0.022 00:57
r24324 | azawawi++ | [Syntax::Highlight::Perl6] removed archived releases
pmichaud which release? 00:58
|mjk| perl6ʲôʱ􏿽xBA􏿽xF2􏿽xBF􏿽xC9􏿽xD2􏿽xD4􏿽xD5􏿽xFDʽ􏿽xB7􏿽xA2􏿽xB2􏿽xBC􏿽xA3􏿽xBF 01:34
slavik english?
|mjk| When will perl6 be ready? 01:43
jnthn Depends on your definition of ready. 01:48
Ready enough that you can play with it and start to learn it - people are already doing this.
Ready to use in production - don't know yet.
meppl good night
slavik jnthn: what about mod_php or something and mod-rewrite to have php call proper p6 scripts? 01:49
instead of mod_perl6
jnthn slavik: Why? 01:50
You'd likely get better performance out of using mod_perl6.
slavik since i can't get mod_parrot to work
jnthn Ah.
Yes, I did manage...after 2 hours.
slavik I get segfaults when apache tries to start 01:51
err ...
jnthn But it's not so trivial.
Oh, I didn't mange to make it segfault. Congrats... :-)
Any luck getting a backtrace though?
I'm sure jhorwitz would be interested to see that. 01:52
slavik no 01:53
jnthn OK. It'd be helpful to know why mod_parrot explodes for you. 01:54
slavik I know
jnthn A backtrace would maybe help to determine why, if it happens insdie something we have built a debug version of.
slavik but jhorwitz never saw it segfault ... maybe I'll checkout a new version mod_parrot and try again
jnthn Try latest, yes.
But if there's still a bug, a bt would be worth trying for. 01:55
ron_ rakudo: my $x; say $x, 2; my $y = undef; say $y, 2; 02:11
p6eval rakudo 33843: OUTPUT[2␤Use of uninitialized value␤2␤]
ron_ Why is the second output different from the first? 02:11
jnthn ron_: Because we initialize to Object, but undef sticks a Failure object in there, I guess. 02:14
ron_ rakudo: my @a; @a[ 1 ] = 'b'; say @a; 02:17
p6eval rakudo 33843: OUTPUT[Null PMC access in get_string()␤current instr.: 'print' pc 15491 (src/builtins/io.pir:22)␤]
ron_ rakudo: my @a = (undef, "b"); say @a; 02:18
p6eval rakudo 33843: OUTPUT[Use of uninitialized value␤b␤]
jnthn Why on earth the error...
rakudo: my @a; @a[1] = 'b'; say @a;
p6eval rakudo 33843: OUTPUT[Null PMC access in get_string()␤current instr.: 'print' pc 15491 (src/builtins/io.pir:22)␤]
jnthn rakudo: my @a; @a[1] = 'b'; say @a[0]; 02:19
p6eval rakudo 33843: OUTPUT[Use of uninitialized value␤␤]
ron_ rakudo: my @a; @a(2) = 'c'; say @a.perl; 02:20
p6eval rakudo 33843: OUTPUT[invoke() not implemented in class 'ResizablePMCArray'␤current instr.: '_block11' pc 38 (EVAL_12:22)␤]
ron_ rakudo: my @a; @a[2] = 'c'; say @a.perl;
p6eval rakudo 33843: OUTPUT[Null PMC access in find_method()␤current instr.: 'parrot;List;perl' pc 3508 (src/classes/List.pir:191)␤]
pmichaud ah, the other elements aren't coming back as undef in the array.
so it's not able to do the string stuff because @a[0] and @a[1] are null. 02:21
jnthn Aye.
pmichaud (and that forces the exception)
yeah, I can fix that.
ron_ Code is in List.class I think ...
jnthn I figure it's probably an easy fix while you've got that bunch of stuff in your head.
ron_ List.pir
pmichaud I think I can put together a quick fix -- the real fix is to get Nil working properly.
and Failure as a Role. 02:22
ron_ OK ... I'll go look for something also to hack at :) ...
jnthn Oh, yes, we need to do Nil.
pmichaud I have a simple version in place, but it's still very simple.
jnthn I'll stick it in next week on Rakudo day.
Oh, OK.
Did you make return; use it?
pmichaud not yet. 02:23
but that's on my list also, unless you beat me to it.
jnthn Maybe on Rakudo day. It'll be a ticket to close if I do it. :-)
pmichaud I just needed it for some of the Positional stuff.
jnthn And we've some way over 150 right now.
pmichaud my $a; should initialize $a to ... ?
jnthn We agreed Object last time we discussed this.
I do ponder though 02:24
pmichaud the proto?
jnthn Now Failure is a role
Yes, the proto
Object with Failure role mixed in?
pmichaud I'm thinking it should be an empty instance of Object
yes, with Failure mixed in.
jnthn Right. That'd give us the uninit warning?
pmichaud yes.
jnthn Great.
pmichaud the tricky part is that I'm not sure that my $a; say $a; # "Object"?
jnthn Doesn't Failure mix something in to deal with that? 02:25
Oh, probably not...
pmichaud Oh, probably yes, actually. Good point.
jnthn It does?
OK, good.
pmichaud well, it should in this case.
jnthn I guess it's a warning and an empty string.
pmichaud right.
my $a; should be pretty close to my $a = undef;
so, whatever undef() returns, that's probably what my $a; shold initialize to. 02:26
...which just means we have to figure out what undef() returns. :-)
because for my @a; @a[2] = 'b'; that's what @a[0] and @a[1] should return :-P
jnthn :-) 02:27
I think it may be more interesting for typed vars.
pmichaud well, in the case of typed vars we know that it initializes to the proto 02:28
jnthn I'm sure if this is correct, but at one point I thought my Int $x; ... $x = undef;
...yes, exactly.
pmichaud my Int $a; say $a "Int" doesn't bother me.
jnthn But for $a = undef; later on
pmichaud it still keeps the type constraint.
it's just not an Int.
jnthn Is it the Int proto with the Failure role mixed in?
pmichaud I think it's just whatever undef returns.
jnthn Because Int proto with Failure mixed in was what I thought it would be. 02:29
Ah.
That wouldn't be sensitive to the type at all.
pmichaud correct.
that's the way I read the spec at the moment.
jnthn OK, in that case I must have been wrong.
The two don't really hang together
pmichaud The theory being that any sort of Exception coming back from an operation can be successfully stored in the variable.
jnthn *nod*
pmichaud (without being immediately thrown, or causing a typemismatch)
jnthn Right. Failure is always acceptable. 02:30
.oO( Don't quote that one out of context... )
pmichaud so I would expect: my Int $a; $a = undef; $a .= new; to throw an exception or something.
jnthn Yes.
Probably a MissingMethodException.
Erm, that's .Net. D'oh. :-) 02:31
pmichaud MissingDotNetExcep... hey wait, that's a bonus!
jnthn spent quite a few days in .Net internals
pmichaud so, does Object+Failure need to be a mixin? 02:32
and don't mixins (currently) create a new class for each mixin?
jnthn Yeah.
pmichaud that's not good.
jnthn Can we not get away with just creating one?
pmichaud that's why I was thinking about Nil
Nil has Failure properties 02:33
jnthn OK, we don't _have_ to create a new class every time.
We can optimize it to not do that.
I just counted it as an optimization and didn't bother with it yet.
pmichaud oh, I agree(d) with that approach. 02:34
still do.
I'm just working out the Failure modes.
jnthn ;-)
ron_ Is there anything I can do to save you all time in terms of filing a perlbug for these issues. (presumably just one perlbug)
jnthn Pun Win.
pmichaud ron: put the example you came up with in an email to [email@hidden.address] 02:35
that way it won't be forgotten, and someone will turn it into a test.
or, if you want to turn it into a test, that'd be great also. :-)
ron_ ok ... will do tomorrow .. good night
pmichaud (it might actually be fixed by tomorrow :-)
jnthn ron_: Night and thanks for flagging up the bug. 02:36
pmichaud okay, time for me to work on getting everyone to bed. 02:37
Don't go there.
:-)
jnthn ...
pmichaud bbiaw
pmichaud @tell jnthn you're correct, assigning a Failure object to a typed container causes it to take on the type of the container. S02:871. 03:51
lambdabot Consider it noted.
Tene So, about spectests... when they rely on other behavior not relevant to the specific features being tested, should I rewrite them to only test that specific behavior? 04:57
PerlJam Tene: I sou^H^Hwould 05:00
er, I would 05:01
(weird laggy effects here)
slavik rakudo: say soemthing 05:43
p6eval rakudo 33844: OUTPUT[Could not find non-existent sub soemthing␤current instr.: '_block11' pc 13 (EVAL_13:13)␤]
slavik pmichaud: any chance for perl on symbian? 05:45
slavik now it core dumps 06:23
azawawi hi there 07:01
pugs_svn r24325 | moritz++ | [S29] List.sort with a unary or nullary code object does a Schwartzian 09:32
r24325 | moritz++ | Transform. (Feel free to improve the wording)
moritz_ rakudo: say (a => 3, c => 1, b => 2).sort({ .value}).perl 09:34
p6eval rakudo 33846: OUTPUT[[("c" => 1), ("b" => 2), ("a" => 3)]␤]
azawawi moritz_: what is stored in the "lex" directory that is generated when using STD.pm? 09:41
moritz_ azawawi: the lexing cache 09:42
moritz_ azawawi: bascially digraphs and the rules that they match 09:43
azawawi documents it in his module... thx ;-)
is there an option in STD.pm to switch caching off? 09:44
moritz_ no 09:45
azawawi what about the foo.pl.log file that is created when using it? 09:46
pmurias ruoso: do you think using MooseX::Declare in mildew is sane? 10:04
pugs_svn r24326 | azawawi++ | [Syntax::Highlight::Perl6] POD fixes, diagrams, ..etc
r24326 | azawawi++ | [Syntax::Highlight::Perl6] Removed a unicode wide-char
r24326 | azawawi++ | [Syntax::Highlight::Perl6] parse_trees() method now returns the correct array of records
pugs_svn r24327 | azawawi++ | [Syntax::Highlight::Perl6] Bumped version to 0.023 10:22
r24327 | azawawi++ | [Syntax::Highlight::Perl6] More POD fixes
rakudo_svn r33850 | bernhard++ | [codinstd] remove trailing space 10:50
pugs_svn r24328 | azawawi++ | [Syntax::Highlight::Perl6] added 4 tests 11:27
r24328 | azawawi++ | [Syntax::Highlight::Perl6] update Changes
pmurias perl6: class Foo { method foo {say "bar";return &self;}};my $foo = Foo.new;my $bar = $foo.foo; 11:35
p6eval elf 24328: OUTPUT[/home/evalenv/pugs/misc/elf/elf_f_src/STD_red/match.rb:141:in `block in to_dump0': undefined method `to_dump0' for true:TrueClass (NoMethodError)␤ from /home/evalenv/pugs/misc/elf/elf_f_src/STD_red/match.rb:140:in `each'␤ from
../home/evalenv/pugs/misc/elf/elf_f_src/STD_red/match.r...
..pugs, rakudo 33851: OUTPUT[bar␤]
pmurias perl6: class Foo { method foo {say "bar";return &self;}};my $foo = Foo.new;my $bar = $foo.foo;$bar().foo
p6eval pugs: OUTPUT[bar␤*** Undeclared variable: ("$__SELF__",MkPad (padToList [("$_",PELexical {pe_type = (mkType "Scalar"), pe_proto = <Scalar:0xb62e4cc9>, pe_flags = MkEntryFlags {ef_isContext = True}, pe_store = <ref:0xb62fc6a1>}),("@_",PELexical {pe_type = (mkType "Array"), pe_proto = <Array:0x...
..elf 24328: OUTPUT[/home/evalenv/pugs/misc/elf/elf_f_src/STD_red/match.rb:141:in `block in to_dump0': undefined method `to_dump0' for true:TrueClass (NoMethodError)␤ from /home/evalenv/pugs/misc/elf/elf_f_src/STD_red/match.rb:140:in `each'␤ from
../home/evalenv/pugs/misc/elf/elf_f_src/STD_red/match.r...
..rakudo 33851: OUTPUT[bar␤invoke() not implemented in class 'Undef'␤current instr.: '_block11' pc 95 (EVAL_13:35)␤]
pmurias is self a function or a keyword? the spec is unclear 11:37
pugs_svn r24329 | azawawi++ | [Syntax::Highlight::Perl6] tests cover every public method (23 tests in total) 12:01
pugs_svn r24330 | azawawi++ | [Syntax::Highlight::Perl6] Fixed a typo in test description 12:12
r24330 | azawawi++ | [Syntax::Highlight::Perl6] Updated the Changes file to 'svn log'... Releasing 0.023
ruoso @tell pmurias MooseX::Declare is a cool module, it certainly could be used 12:28
lambdabot Consider it noted.
pmurias ruoso: hi 12:42
lambdabot pmurias: You have 1 new message. '/msg lambdabot @messages' to read it.
ruoso hi pmurias 12:44
pmurias ruoso: do you think it is sane to treat self as a keyword? 12:45
ruoso unfortunally, it isn't one 12:46
but there's a simple way of making it work
we just need to add &self := { $capture.invocant } in the AdhocSignature for methods
pmurias how far is a &say in the prelude in the ROADMAP? 12:48
ruoso pmurias, I didn't want to implement &say before having multi sub implemented 12:50
pmurias ok 12:52
i'm getting annoyed by $OUT.print and was thinking a placeholder sub say($arg) {$OUT.print($arg.FETCH)} would be nice 12:53
ruoso pmurias, yeah... maybe we could just have something that would be replaced later 13:28
pmurias ruoso: so it's more of a question when will we have a prelude 13:33
ruoso: self is handled by term:self so maybe it's a keyword after all
You may always access the 13:34
current invocant using the keyword C<self>.
S12:164
S12:188 mentions it's a function 13:36
TimToady: is self a keyword or a function, in other words is &self legal?
ruoso hmm 13:48
that makes me think... if self is not a function, we might need to store the invocant in a different variable 13:49
and self would mean accessing that variable
is there a twigil for runtime-specific variables?
$¿var as opposed to $?var :D 13:50
pmurias seems sane 13:51
ruoso so $¿invocant ? 13:52
pmurias yes... ;)
ruoso pmurias, are you aware that " ¿ statement ? " is the way to ask a question in written spanish 13:56
?
that make $¿invocant? funny
pmurias no
i wasn't aware of that
ruoso we need to declare '$¿invocant := $capture.invocant' in the AdhocSignature for methods 14:01
pmurias should it be invocant or self? 14:02
ruoso hmm... $¿self might make more sense
masak is that a new twigil? 14:03
pmurias yes
SamB huh -- " ¿ statement ? " doesn't look good here
masak ¿what does it mean?
SamB because ¿ and ? don't seem to be in the same font ... 14:04
pmurias changes to $¿invocant to $¿self
masak: evil runtime variable
SamB too bad the text renderer can't just transform the glyph for ? to get the one for ¿ ...
masak pmurias: ah. because there wasn't enough evil in Perl 6?
ruoso we needed a way to implement self 14:05
masak I've always seen it as a keyword, fwiw
SamB but Self has only been implemented ONCE
ruoso masak, yes... it is a keyword, $¿self is how we're going to implement that keyword in mildew
masak ruoso: ok. 14:06
SamB in C++ that depends heavily on the way the compiler lays out classes with vtables!
hmm, mildew does not sound good somehow
pmurias masak: there seems to be a serious deficiency of evil in Perl 6 ;) 14:07
masak pmurias: yes, no-one has addressed that satisfactorily so far. 14:08
so, good work. :)
pugs_svn r24331 | pmurias++ | [mildew] self support 14:09
r24331 | pmurias++ | [m0ld] pcl is linked in so --exec works again
pmurias ruoso: p6opaque should implement ^!clone? 14:16
ruoso yes, it should
pmurias SamB: re vtables mildew is a very naive compiler now as we attempt to layer stuff to aim for a faster bootstrap instead of trying to compile down to the metal 14:18
SamB pmurias: btw I was actually speaking of the Self language ;-P 14:19
pmurias ruoso: i should add an ^!instance_storage method to p6opaque? 14:25
ruoso yeah... it makes sense 14:29
pugs_svn r24332 | mj41++ | [Synopses] - some formating 15:06
r24333 | mj41++ | util/PaP6-testing - README fix 15:10
azawawi hi 15:29
pmichaud oh cooooooool 15:30
sort { .whatever } @list is *already* in the synopses
jnthn (knowing a block's arity)++
jnthn is happy to see this added 15:31
pmichaud it's in Synopsis 3, under the file test operators :-)
The advantage of the method form is that it can be used in places that
require tighter precedence than C<~~> provides:
sort { $^a.M <=> $^b.M }, @files
though that's a silly example since you could just write:
sort { .M }, @files
masak pmichaud: you should write that to the current thread in p6l :)
pmichaud I am.
masak pmichaud++
azawawi moritz_: plz take a look at search.cpan.org/perldoc?Syntax::Highlight::Perl6 15:32
jnthn Either way, it's worth a mention in S29.
pmichaud that's how I found it -- I was about to write to the thread saying "this is how we would do the -M example now", only to discover it's already in S03
masak jnthn: moritz_++ put it in already.
jnthn Aha, great. 15:33
pmichaud adds the comment to his post as well.
azawawi @tell TimToady I've documented the bugs i encountered so far in search.cpan.org/perldoc?Syntax::Highlight::Perl6 . Can we dump Moose.pm dependency for STD.pmc? Moose seems not to work correctly on my strawberry win32. Thx. TimToady++ 15:39
lambdabot Consider it noted.
mj41 hi, is "=begin code :allow<B>" valid POD syntax? 15:44
pmichaud perl 6 pod? yes, I think so -- I haven't reviewed the spec lately. It might not be implemented yet.
mj41 it is used inside S26-documentation.pod .. line 73, ... 15:45
pmichaud I know that S26 is up for some more revision, but whatever appears in S26-documentation.pod is currently our best guess at things. 15:46
mj41 and I can't use Pod::Simple::Wiki to generate S26 on perl6.cz/wiki/Synopses/en 15:47
pmichaud well, note that Perl 6 pod is different from Perl 5 pod
I don't know if Pod::Simple::Wiki supports p6pod 15:48
mj41 I know. So we are using Perl 6 POD or Perl 5 POD to write Synopses? 15:49
pmichaud S26 is written in Perl 6 POD
the others may still be p5pod, if only because we don't have a p6pod formatter yet.
eventually they will become p6pod
jnthn tries to work out what perl6.cz/wiki/Jonathan_Worthington says about him.
mj41 pmichaud Thanks. 15:51
masak is there a way to limit the number of allowed parameters to a code block argument in a signature? 15:52
jnthn Implemented, or just at all? 15:53
masak just at all.
this is #perl6, after all :)
jnthn well
there's always
the (probably working)
sub foo(&code_block where { 1 <= .arity <= 2 }) { ... } 15:54
masak I was thinking somthing like that.
masak goes away to try that
jnthn Mwahaha. I just realized. If that works you can multi-dispatch on the arity of the block you're passed. :-)
pmichaud oh!
masak jnthn: yes :) 15:55
pmichaud that answers a few other questions I had as well.
cool.
jnthn pmichaud: It should even work in Rakudo today.
masak rakudo: sub foo(&code_block where { 1 <= .arity <= 2 }) { say "OH HAI" }; foo(1)
p6eval rakudo 33858: OUTPUT[Method 'arity' not found for invocant of class 'Int'␤current instr.: '_block23' pc 417 (EVAL_14:163)␤]
masak what does Int have to do with it?
pmichaud masak: you didn't pass a code block.
jnthn Int?
Oh!
Yes. :-)
pmichaud you sent it an Int.
masak oh. 15:56
jnthn we should fail with "Doesn't do Callable".
masak jnthn: rakudobug?
pmichaud no, we should fail with "no matching sub found"
jnthn If you like.
masak files
pmichaud (if multi sub)
jnthn It wasn't a multi
pmichaud right
masak expects more bugs from this
jnthn It'd be parameter type check failed in sub foo at the moment
pmichaud right.
that's what I meant. 15:57
really.
jnthn But I'm certainly up for more explanation of *why*.
pmichaud :-)
jnthn multis are now quite good about this
If you get an ambiguous dispatch it gives you .perl on the signatures of the ambiguous candidates.
masak rakudo: multi foo(&c where { .arity == 1 }) { say "One." }; multi foo(&c where { .arity == 2 }) { say "Two." }; foo({ $^a }); foo({$^a + $^b}) 16:02
p6eval rakudo 33858: OUTPUT[One.␤Two.␤]
masak wow, it works!
jnthn
.oO( Phew! )
 16:02
masak jnthn++ 16:03
jnthn notmasakbug++ ;-) 16:04
masak rakudo: multi foo(&c where { .arity == 1 }) { say "One." }; multi foo(&c where { .arity == 2 }) { say "Two." }; foo({$^a + $^b + $^c })
p6eval rakudo 33858: OUTPUT[Ambiguous dispatch to multi 'foo'. Ambiguous candidates had signatures:␤:(Any c where all({ ... }))␤:(Any c where all({ ... }))␤␤current instr.: '_block11' pc 35 (EVAL_14:19)␤]
masak that's wrong, though.
as far as I can see.
why is the dispatch ambiguous? 16:05
pmichaud because none of them matched.
"ambiguous" is probably the wrong word.
masak yes.
it really is.
jnthn That's...interesting. :-S
pmichaud change it to be "Failed dispatch to ..." 16:06
masak submits rakudobug
jnthn It's not just wording. It really did think it was an ambiguity.
masak exactly.
jnthn rakudo: multi sub foo(Int $x) { }; foo("OH HAI")
p6eval rakudo 33858: OUTPUT[No applicable candidates found to dispatch to for 'foo'␤current instr.: '_block11' pc 31 (EVAL_14:17)␤]
jnthn *nod*
pmichaud okay.
jnthn Interesting bug. 16:07
Shouldn't be too hard to fix.
masak jnthn++ 16:08
jnthn masak++ # finding these 16:09
These will make good test cases.
masak it's a pleasure. and it's good both for me and for Rakudo. 16:10
masak what's the easiest way to make an object with attributes that cannot be (easily) changed after the object's instantiation? 16:20
pugs_svn r24334 | azawawi++ | [Syntax::Highlight::Perl6] Added perl6.vim to the module (Text::VimColor support)
pmichaud you mean "not easily changed, even by the object itself"? 16:21
masak pmichaud: no, I'm the class author, so I control the object.
pmichaud isn't that just a private attribute, then?
masak pmichaud: a private attribute can still be initialized on creation?
pmichaud yes.
masak goodie.
thanks.
jhorwitz pmichaud: i have an issue with list assignment, though it might have something to do with the implementation of "split" 16:24
i shall nopaste
nopaste?
pasteling "jhorwitz" at 96.245.16.64 pasted "pmichaud: list assignment fail" (28 lines, 894B) at sial.org/pbot/33663 16:26
pmichaud ah, list assignment needs generate Failure objects for the things that don't get assigned. 16:27
or throw an exception.
jhorwitz want me to open a ticket? 16:28
pmichaud sure
I'm going to clean up failures this morning, and then I'll do that.
then I'm going to work on tickets for a while. 16:29
jhorwitz excellent. :)
pmichaud I'll probably do parameter stuff tomorrow-ish.
oh, I also need to do PGE assertions.
pmichaud maybe I should stick this stuff in my hiveminder queue :-) 16:29
jhorwitz don't forget world peace
jnthn pmichaud probably saw how I hacked around lack of PGE assertions and has been horrified into doing them. ;-)
pmichaud I haven't seen it yet, no. 16:30
jnthn You probably don't want to. ;-)
pmichaud but as soon as you mentioned <?{{...}}> yesterday I knew how to do it.
the horror for me generally starts when jonathan++ says "I think I'll implement <some cool feature that looks really hard to Pm>"
:-)
but it's a nice sort of horror, because... well -- see "passing spectests" :-) 16:31
pugs_svn r24335 | azawawi++ | [Syntax::Highlight::Perl6] Added vim_html() for Text::VimColor & perl6.vim 16:32
r24335 | azawawi++ | [Syntax::Highlight::Perl6] Bumped version to 0.025
r24335 | azawawi++ | [Syntax::Highlight::Perl6] Added tests for vim_html and remove version from README
jnthn Our inability to agree on what the hard bits are continues to serve Rakudo well. :-) 16:34
pmichaud afk, grocery shopping 16:35
jhorwitz pmichaud: fyi, list assignment bug w/ split is RT #61336 17:06
Hinrik mj41: the only Perl 6 Pod translator I've seen is Perl6::Perldoc, you might want to take a look 17:13
pugs_svn r24336 | hinrik++ | [util/perl6.vim] small replace %\(\s\|$) with \_s 17:16
azawawi hinrik: im nearly done with the vim_html() method in Syntax::Highlight::Perl6; This will use perl6.vim if you installed it in $HOME/.vim/syntax 17:17
Hinrik ok
hm, from S02: "Unlike in Perl 5, if a sigil is followed by comma, semicolon, colon, or any kind of bracket or whitespace (including Unicode brackets and whitespace), it will be taken to be a sigil without a name rather than a punctuational variable. This allows you to use sigils as coercion operators" 17:20
a colon? but a colon is a twigil, right? 17:21
jnthn $:named_placeholder_param, IIRC.
Hinrik: What context are we in here though? Signatures? 17:22
Oh, probably not, reading that. Hmm.
Hinrik It's under the Names heading in S02
jnthn Maybe LTM decides it? 17:23
Or not even that
$:@foo # can't be a variable name (though I'm not sure what it means) 17:24
$:foo # named palceholder
$: foo # can't be a variable name, becuse of the sapce, so calls foo
TimToady $: used to be a list operator, but now it's just $ args
lambdabot TimToady: You have 3 new messages. '/msg lambdabot @messages' to read them.
jnthn Is $: foo meaning anythng now?
TimToady btw, can someone tell me which hemisphere I'm in today? 17:25
jnthn Probably northern?
TimToady $:foo is the twigil now
jnthn Copenhagen?
TimToady maybe Many Worlds?
Hinrik is "$: $foo" an error? 17:25
TimToady should be 17:26
jnthn Not always, probably
Hinrik ok
jnthn sub foo($: $foo) { ... } # we take some scalar invocant...
Where : here is the invocant separator in a signature.
TimToady yes, STD thinks it's an error (as rvalue) 17:27
Hinrik hm, how could you have a non-scalar invocant?
jnthn When you call eg %hash.keys 17:28
TimToady hmm, currently STD requires a space between $ and : in a sig
Hinrik ah 17:28
jnthn TimToady: What about sub foo($self: $foo) { ... } 17:29
?
No space there?
TimToady that seems fine to STD
might just be the bare sigil form of parameter is too picky 17:30
well, can't really look at it right now--don't even have time to backlog yet... 17:31
bbl &
pugs_svn r24337 | azawawi++ | [Syntax::Highlight::Perl6] Support for Text::VimColor is now complete 17:40
r24337 | azawawi++ | [Syntax::Highlight::Perl6] You have to install perl6.vim by yourself
r24337 | azawawi++ | [Syntax::Highlight::Perl6] Separated vim_html() test to 01-vim.t
r24338 | hinrik++ | [util/perl6.vim] updated todo list 17:41
r24339 | azawawi++ | [Syntax::Highlight::Perl6] vim_html will generate inlined full html 17:45
r24340 | azawawi++ | [Syntax::Highlight::Perl6] Updated Changes... Releasing 0.024 soon. 17:51
r24341 | azawawi++ | [Syntax::Highlight::Perl6] last min pod fix... 17:54
pugs_svn r24342 | lwall++ | [t/spec] fix syntax errors found by STD 18:47
pugs_svn r24343 | lwall++ | [STD] report non-associative errors correctly 18:50
r24343 | lwall++ | [Cursor,gimme5] cleanup of logging, some small speedups
rakudo_svn r33861 | pmichaud++ | [rakudo]: spectest-progress.csv update: 240 files, 5005 passing, 0 failing
azawawi moritz_, hinrik: should we submit perl6.vim to www.vim.org/scripts/ for inclusion? 19:06
pugs_svn r24344 | azawawi++ | [Syntax::Highlight::Perl6] Renamed Actions package to Syntax::Highlight::Perl6::Actions 19:21
Hinrik azawawi: hm, maybe when I finish a few more things :P 19:26
some(most?) of the regex/rule stuff in perl6.vim is broken, for example, I haven't touched it yet
azawawi Hinrik: cool 19:34
Hinrik: i've already included perl6.vim support in my highlighter package... fyi 19:38
pugs_svn r24345 | azawawi++ | [Syntax::Highlight::Perl6] STD_syntax_highlight is now using this package
rakudo_svn r33863 | pmichaud++ | [rakudo]: Remove unused global lookup. 20:10
Hinrik ok, cool 20:12
pugs_svn r24346 | hinrik++ | [util/perl6.vim] add todo item 20:17
rakudo_svn r33864 | pmichaud++ | [rakudo]: Fix problem with null elements passed to print (partial fix RT #61324). 20:20
Hinrik rakudo: say <a b # comment>.perl 21:05
p6eval rakudo 33864: OUTPUT[["a", "b", "#", "comment"]␤]
Hinrik rakudo: say «a b # comment».perl
p6eval rakudo 33864: OUTPUT[Statement not terminated properly at line 1, near "\x{ab}a b # com"␤␤current instr.: 'parrot;PGE;Util;die' pc 129 (runtime/parrot/library/PGE/Util.pir:83)␤]
jnthn Ah, that might just be our unicode parsing bug. 21:07
Hinrik rakudo: say <<a b # comment>>.perl
p6eval rakudo 33864: OUTPUT[["a", "b", "#", "comment"]␤] 21:08
Hinrik hm
S02 says that «» allows comments 21:09
pugs: say <<a b # comment>>.perl
p6eval pugs: OUTPUT[("a", "b", "#", "comment")␤]
Hinrik that should fail because the comment should consume the >> 21:13
perl6: say <<a b #[comment] c d>>.perl 21:15
p6eval rakudo 33864: OUTPUT[["a", "b", "#[comment]", "c", "d"]␤]
..elf 24346: OUTPUT[["a"]␤]
..pugs: OUTPUT[("a", "b", "#[comment]", "c", "d")␤]
rakudo_svn r33865 | pmichaud++ | [rakudo]: Fix initialization of $/, $0, etc. (RT #57758) 21:20
r33865 | pmichaud++ | * undef objects now return undef when subscripted
r33865 | pmichaud++ | * reorganized Failure.pir methods
pugs_svn r24347 | hinrik++ | [util/perl6.vim] expect an identifier as a :key, allow comments and escaped # chars in double angles, fix problem with nested angles in some Pod formatting codes 21:32
pugs_svn r24348 | hinrik++ | [util/perl6.vim] made operator matching less greedy, which fixes a few problems 21:42
pugs_svn r24349 | putter++ | [elf_h] EmitSimpleP5: postcircumfix {} [] special cases dropped. Match: fields renamed, and array field added. 21:56
r24350 | putter++ | [rx_on_re] Use elf_h's Match. 22:04
r24350 | putter++ | t_baseline.result: some error messages changed.
r24350 | putter++ | t/re_tests.pl, t/rx.pl: don't use overloading to access Match (embedded code tests still use overloaded bool - todo?).
pugs_svn r24351 | hinrik++ | [util/perl6.vim] highlight $<match> more like a variable with a special sigil 22:08
pugs_svn r24352 | hinrik++ | [util/perl6.vim] highlight punctuation and numeric variables, adjust highlighting of twigils 22:26
pugs_svn r24353 | hinrik++ | [util/perl6.vim] enhance [] reduce matching a bit 22:43
pugs_svn r24354 | putter++ | [elf_h] Fix regression bug, and avoid dialect expansion. 22:49
r24354 | putter++ | [STD_blue] Sync with elf_h.
mncharity on_sbcl still works. 22:50
mncharity next task for me: fleshing out STD_blue-based regex-source->IR parsing, with a target milestone of the rx_on_re test suite passing(*) using STD_blue-based parsing. (*) To the extent possible given STD bugs parsing rx and re... not a great milestone, but oh well. :/ Then either migrate to the pugs t/ rx and re tests, or start working through STD.pm, not sure which. 23:13
g'night all &
rakudo_svn r33869 | pmichaud++ | [rakudo]: Remove spurious :subid tag from enums.pir. 23:30

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!