pugscode.org/ | nopaste: sial.org/pbot/perl6 | pugs: [~] <m oo se> (or rakudo:, kp6:, smop: etc.) || We do Haskell, too | > reverse . show $ foldl1 (*) [1..4] | irclog: irc.pugscode.org/
Set by TimToady on 25 January 2008.
mncharity me neither. for pugs t/ as "test suite to detect pugs regressions", clearly wrong. for pugs t/ as "current spec", updating to something is clearly right. i suspect the first use is already better served by "check out revision x of t/". and second use is the current intent. so Right I suspect. 00:00
I've just kludge a workaround for now.
*kludged
pugs: int rand 1000 00:04
exp_evalbot RESULT[623]
mncharity rakudo: int rand 1000
exp_evalbot RESULT[Method 'perl' not found for invocant of class 'Float'␤current instr.: '_block10' pc 35 (EVAL_11:16)␤called from Sub 'parrot;PCT::HLLCompiler;eval' pc 785 (src/PCT/HLLCompiler.pir:458)␤called from Sub 'parrot;PCT::HLLCompiler;evalfiles' pc 1067 (src/PCT/HLLCompiler.pir:587)␤called from Sub
..'parrot;PCT::HLLCompiler;command_line' pc 1246 (sr...
mncharity TimToady: (6) int is a typename. also apparently something you can say 'int 3.2' with? no guidance from STD5. any thoughts? 00:10
[particle2 i think =begin description ... =end description 00:11
is better than =begin pod 00:12
it seems more... descriptive
mncharity :) 00:13
mncharity hmm. it's starting to look like my going through pugs t/ looking at STD_red parsefails is going to turn up assorted obsolete p6 in tests. I'm not quite sure how to handle that. :/ 00:16
mncharity (t1) t/02-test-pm/use_ok_test.pm's module name use_ok_test-0.0.1 appears obsolete. 00:18
(t2) lots of test files have an obsolete =kwid...=cut construct. 00:19
(tN) is my new "issues noticed in pugs t/" series.
[particle1 2) notify the mailing list of the problems so somebody else can fix 00:19
wireless--
mncharity (t3) various test files have an obsolete =pod...=cut construct. 00:21
re 'notify the mailing list', #perl6 is logged... anyone welcome to fix... I'll puzzle over what to do with the list later... 00:22
[particle]ventus i suppose you could also modify your parser to deal with perl 5 pod 00:23
mncharity happily STD_red_run provides a nice place to s///g the oddball pod comments away. 00:25
hmm. which breaks line numbering (at least as currently simply implemented). ah well. hasn't been an issue yet. 00:26
[particle]ventus then fix line numbering by commenting out the pod rather than deleting it 00:27
mncharity [particle]ventus: oh, right. duh. tnx 00:33
still breaks character numbering, but that's less important. usual solution is to tr/.\n/ \n/ or some such. 00:34
mncharity TimToady: (7) Is 'f(:x(1) :y(2))', no comma, still valid? if STD.pm parses it, could you give me a hint? tnx. 00:54
mncharity pugs: \42 01:09
exp_evalbot RESULT[\42]
mncharity rakudo: \42
exp_evalbot OUTPUT[Syntax error at line 1, near "\\42"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;Perl6::Grammar;TOP' pc 11308 (src/gen_grammar.pir:249)␤called from Sub 'parrot;PCT::HLLCompiler;parse' pc 564
..(src/PCT/HLLCompiler.pir:348)␤called from Sub 'parrot;PCT::HLLCompiler;compile' pc ...
mncharity (t 01:10
(t4) t/builtins/perl.t has a '# References to scalars' section. do those exist anymore? 01:11
(t5) t/oo/from_moose/ is a year-old collection of p5 code, apparently awaiting translation to p6. curious. 01:23
Eevee bah I should really take a shot at that whole test migration thing 01:27
I think I am shy about touching "someone else's" code
mncharity could start with t/oo/from_moose/ :) get your feet wet. update the p5 files from the current Moose, and then start translating... though... 01:29
that said, there may be a reason why things apparently stalled out a year ago. ie, it may be hard. or non-useful? or... something.
mncharity yiyihu: ^^^ any guidance? 01:30
Eevee or everyone was busy with something deemed more useful than writing tests? :P a pitfall I frequently (if not constantly) fall into
mncharity could be :)
Eevee holy 01:34
there are a lot of tests in here
Eevee oh, all tiny 01:35
mncharity and the ones I glanced at seem to become even smaller in p6 01:41
Eevee and all of them are .orig except the first 01:42
someone had grandiose plans and promptly abandoned them
mncharity or perhaps the plan was to set things up so someone else could work on it. ;) 01:45
Eevee hum. svn log claims the tests are synced with moose's repo 01:54
mncharity I believe that's a intent/policy, rather than mechanism. Moose now 0.23. :) 01:56
Eevee there are also no "hey automatically syncing" sorts of commits 01:57
of course, if these are all translated to p6 there's not much hope of keeping them sync'd any more
mncharity I suspect the idea was "here is a set of p6-like oo tests we can copy/translate from, rather than having to think of them ourselves". so a close sync isn't really needed. 02:01
Eevee moose is now 0.*4*3 02:04
mncharity I point you at from_moose only because it seemed one way to avoid dealing with "someone else's" code. all this can be yours... don't know if it's an "optimal" task. but if taken lightly (ie, look for any low hanging fruit; don't get bogged down or discouraged), it could be a "get your feet wet" thing to play with for a bit.
and a way to learn Moose :) 02:05
Eevee and a way to learn p6's object system, which is no doubt almost, but not quite, entirely unlike what I remember 02:06
mncharity for any value of remember :) 02:07
my recent favorite was my Int $I_am_undef; say $I_am_undef; #=> "Int" 02:08
or something vaguely like that 02:09
Eevee yeah I saw discussion of that either here or in #parrot
mncharity svnbot looks to be on vacation. could someone poke it?
Eevee given how many undef warnings I see even now in production perl5, that might not be a good idea for default behaviour.. especially if it doesn't even warn 02:10
mncharity my impression is all sorts of interesting and helpful behavior can be available, both at compile and runtime. 02:12
mncharity ok. brain is toast. current dev path is () keep banging STD_red against t/ until ~80% of tests are not noisily and obviously parsefailing (vs current 40%). then () start banging elf against t/, attempting to actually pass them. 02:15
Eevee how much OO does rakudo support anyway?
mncharity assuming the misparses and tree defects aren't too bad, that second part may actually be fun. :) 02:16
re oo rakudo, I've little idea, sorry.
Eevee make spectest then 02:17
mncharity elf oo is still quite primitive (no submethod's, etc, etc). 02:20
mncharity and in some respects, is likely to remain so until someone else takes it on. I'm more focused on passing t/ as a way of getting people interested/started, so p6opaque and really conformant oo is not on my agenda. 02:21
Eevee it occurs to me that there should be a perl 6 glossary 02:22
mncharity "enough fast fake p6 oo for you to write a p6 compiler in it"
I believe there is one, let's see...
Eevee the perl culture likes to invent clever terms not commonly used elsewhere
mncharity www.perlfoundation.org/perl6/index....and_jargon 02:23
lambdabot Title: Glossary of Perl 6 Terms and Jargon / Perl 6, tinyurl.com/ytvdje
Eevee I've seen that, but I mean things like submethod/metaoperator/hyperoperator/multimethod/etc
mncharity ah, sort of an index into feather.perl6.nl/syn/ 02:24
lambdabot Title: Official Perl 6 Documentation
wknight8111 I second that motion, there are a lot of clever terms, and it takes a while for people to get up to speed
I'm a living example, I still can't decipher half the stuff that gets said around here
Eevee yeah 02:25
mncharity motion carried unanimously
Eevee I think even some of the synopses talk about invented vernacular as though the reader had heard it before
which is a bit silly when the synopses invented it in the first place
mncharity "Getting started with the Official Perl 6 Documentation - a orienting glossary and introduction" ? :) 02:27
elf - "enough fast fake p6 oo for you to *happily* write a p6 compiler in it" 02:28
end of day. good night all & 02:29
Eevee night
mncharity TimToady: (8) given '3 if 4;', statement calls <?stdstopper>, which is true because it checks <statement_mod_cond>. but because <?stdstopper> is true, we never get to the || branch which would actually parse <statement_mod_cond>. or am I missing something? 04:28
& 04:29
moritz_ nqp: my $x = 3; say $($x) 08:02
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "= 3; say $"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block'
..pc 2928 (src/Grammar_gen.pir:1037)␤called from S...
moritz_ nqp: my $x = 3; say $($x);
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "= 3; say $"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block'
..pc 2928 (src/Grammar_gen.pir:1037)␤called from S...
moritz_ nqp: my $x := 3; say $($x);
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "$($x);"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block' pc
..2928 (src/Grammar_gen.pir:1037)␤called from Sub '...
riffraff hi 08:36
moritz_ hi riffraff, what's up? 08:38
masak mofino: is `my @a, @b;` really legal Perl 6? 12:16
moritz_ masak: did you mean me? ;-) 12:17
masak yes :/
perl -w -Mstrict -e 'my @a, @b;' # gives error
moritz_ perl 5 needs parenthesis around some of these lists 12:18
my (@a, @b); works
masak yes, I know
I was referring to the parentheses
can you leave them out in p6?
moritz_ and Perl 6 removes the need for all those list constructing arrays
just like you can say 'for 1, 2, 3, 4 { ... }' 12:19
masak so `my $a, $b, $c = 1, 2, 3;` does what I mean?
moritz_ pugs: my $a, $b, $c = 1, 2, 3; say $b
exp_evalbot OUTPUT[*** ␤ Unexpected ","␤ expecting "::"␤ Variable "$b" requires predeclaration or explicit package name␤ at /tmp/O5R76RsF9u line 1, column 10␤]
moritz_ uhm 12:20
masak paraphrasing Yegge: pugs is not a perfect perl 6
moritz_ right
masak but essentially, that's the same error I got from p5
moritz_ but I'm looking at STD.pm right now
and I don't see how it could handle that either 12:21
masak heh
moritz_ pugs: my ($a, $b, $c) = (1, 2, 3); say $b
exp_evalbot OUTPUT[2␤]
moritz_ pugs: my ($a, $b, $c) = 1, 2, 3; say $b
exp_evalbot OUTPUT[2␤]
masak yes, that much is clear to me too
(besides, let's hope that no-one ever logs in as 'pugs' on this channel) 12:22
moritz_ I think diakopter took care of registering 'pugs', 'rakudo' and 'nqp' as freenode nicks 12:23
rakudo: my $a, $b; say 2 12:24
exp_evalbot OUTPUT[Scope not found for PAST::Var '$b'␤current instr.: 'parrot;PCT::HLLCompiler;panic' pc 158 (src/PCT/HLLCompiler.pir:103)␤called from Sub 'parrot;PAST::Compiler;post_children' pc 1226 (src/PAST/Compiler.pir:144)␤called from Sub 'parrot;PAST::Compiler;call' pc 2274
..(src/PAST/Compiler.pir:525)␤called from Sub 'parrot;PAST::Compiler;post_chil...
moritz_ rakudo: my ($a, $b); say 2
exp_evalbot OUTPUT[Scope not found for PAST::Var '$a'␤current instr.: 'parrot;PCT::HLLCompiler;panic' pc 158 (src/PCT/HLLCompiler.pir:103)␤called from Sub 'parrot;PAST::Compiler;post_children' pc 1226 (src/PAST/Compiler.pir:144)␤called from Sub 'parrot;PAST::Compiler;call' pc 2274
..(src/PAST/Compiler.pir:525)␤called from Sub 'parrot;PAST::Compiler;post_chil...
masak pugs: sub bar($x) { $x = 3; } 12:30
exp_evalbot RESULT[\sub :($x) "$_" := "Scalar" #<Scalar:0xb71c8ed4>␤ "$x" := "Scalar" #<Scalar:0xb71c79dc>␤ "&?ROUTINE" := "Sub" #<Sub:0xb6604cec>␤ "&?BLOCK" := "Sub" #<Sub:0xb6604cec> {"&bar" := "Sub" #<Sub:0xb715fa30>, "$_" := "Scalar" #<Scalar:0xb7170d44>␤
.. ...
masak pugs: sub bar($x) { $x = 3; say $x; } my $a = 2; bar($a); 12:31
exp_evalbot OUTPUT[*** Can't modify constant item: VRef <Scalar:0xb68c7a40>␤ at /tmp/0yVkn5MZ73 line 1, column 15-21␤]
masak couldn't that be a compile-time error?
moritz_ it could, if you'd invest enough energy in the semantic analysis 12:45
masak moritz_: I'm almost of the opinion that a correct Perl 6 compiler should disallow such a program 12:47
it's not _that_ much semantic analysis
what we're looking for is an assignment to a variable declared as read-only 12:48
moritz_ masak: you're right, it's *very* desirable 12:49
masak is this not nailed down yet?
if it isn't I'm writing to perl6-lang
moritz_ I don't know 12:51
masak greps synopses first
masak there, mail sent 13:09
spinclad nqp: my $x := 3; say ($($x)) 14:51
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "($($x))"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block' pc
..2928 (src/Grammar_gen.pir:1037)␤called from Sub ...
spinclad nqp: my $x := 3; say ($($x));
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "($($x));"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block' pc
..2928 (src/Grammar_gen.pir:1037)␤called from Sub...
spinclad nqp: my $x := 3; say ($x); 14:52
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "($x);"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block' pc
..2928 (src/Grammar_gen.pir:1037)␤called from Sub 'p...
[particle] no space after say
spinclad nqp: my $x := 3; say($($x))
exp_evalbot OUTPUT[Method 'get_scalar' not found for invocant of class 'Integer'␤current instr.: '_block10' pc 21 (EVAL_4:11)␤called from Sub 'parrot;PCT::HLLCompiler;eval' pc 785 (src/PCT/HLLCompiler.pir:458)␤called from Sub 'parrot;PCT::HLLCompiler;evalfiles' pc 1067 (src/PCT/HLLCompiler.pir:587)␤called from
..Sub 'parrot;PCT::HLLCompiler;command_line' pc 1...
spinclad right
[particle] that's better.
nqp: class Integer { method get_scalar() { say 'hi' } }; my $x := 3; say( $($x) ); 14:55
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "'hi' } }; "␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block'
..pc 2928 (src/Grammar_gen.pir:1037)␤called from S...
[particle] nqp: class Integer { method get_scalar() { say 'hi' }; }; my $x := 3; say( $($x) ); 14:56
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "'hi' }; };"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block'
..pc 2928 (src/Grammar_gen.pir:1037)␤called from S...
spinclad nqp: class Integer { method get_scalar() { say 'hi'; }; }; my $x := 3; say( $($x) );
exp_evalbot OUTPUT[Statement not terminated properly at line 1, near "'hi'; }; }"␤current instr.: 'parrot;PGE::Util;die' pc 120 (runtime/parrot/library/PGE/Util.pir:82)␤called from Sub 'parrot;NQP::Grammar;statement_list' pc 4364 (src/Grammar_gen.pir:1522)␤called from Sub 'parrot;NQP::Grammar;statement_block'
..pc 2928 (src/Grammar_gen.pir:1037)␤called from S...
spinclad nqp: class Integer { method get_scalar() { say('hi') } }; my $x := 3; say( $($x) ); 14:57
exp_evalbot OUTPUT[hi␤1␤]
masak spinclad: cool! 14:57
spinclad 1?
masak spinclad: probably the result from 'say' 14:58
[particle] yep
spinclad cool beans indeed.
masak nqp: class Integer { method get_scalar() { 'hi' } }; my $x := 3; say( $($x) );
exp_evalbot OUTPUT[hi␤]
[particle] nqp has no runtime, so to get $() and @() working, you need to add the functions to the runtime 14:59
s/functions/methods/
spinclad yummy cool beans! must try them in some more recipes
masak salads usually contain cool beans 15:00
spinclad sadly they must get re-added on every line, with evalbot 15:01
[particle] yes, but you have a command line somewhere, i'm sure!
like, feather?
spinclad like home even, true
but for playing in public for our mutual delectation 15:02
or just spamming the channel 15:03
pmurias ruoso: how should code using smop be compiled? 18:01
ruoso you mean using smop as a library? 18:06
pmurias, if so, you can just -lsmop... no special requirements... 18:07
take a look at the tests, they are all stand-alone programs that are compiled agains libsmop
pmurias trying 18:09
how do i specifiy where should gcc look for the object file? 18:14
ruoso -L
iirc
pmurias prepending /bin/sh libtool works ;) 18:23
ruoso I really like autotools ;) 18:24
ruoso not that I undertand them... 18:24
;)
pmurias i hate autotools 18:25
;)
ruoso pmurias, I'm curious... what sort of things are you experimenting? 18:29
pmurias i'm thinking of doing an smop elf backend 18:31
ruoso elf?
pmurias the thing mncharity was working on 18:32
ruoso a little outdated... 18:33
pmurias it's a perl6 implementation with a hand-translitarated from STD parser in ruby 18:34
the none backend part is bootstraped
ruoso ahm... sounds interesting...
pmurias misc/elf
ruoso I should have some time to get back in the end of this month 18:35
than I'll be able to get up-to-date on all of this
pmurias i'll have my school exams over soon, so i'll have more free time at the end of them month too 18:37
ruoso: how are thing going for fglock? he hasn't been on irc lately 18:39
ruoso pmurias, he had recently moved to amsterdam
pmurias & 18:48
rindolf Hi all. 20:07
pmurias rindolf: hi 20:18
rindolf Hi pmurias 20:19
mncharity notes "ruoso: elf?", concludes he's doing something very wrong. :/ 22:11
so let's see, no commits? or svnbot still broken? 22:12
pmurias mncharity: hi 22:13
mncharity hi pmurias. :) 22:14
no commits. :(
pmurias g'night 22:16
mncharity pmurias: re elf and "was working on", still am... just been focused on parsing lately. 22:18
doh. good night...
mncharity it's kind of neat that += is just infix:<+> followed by infix_postfix_meta_operator:<=> . 22:49
+≐ :) 22:52
wow. that even parses (if added as a second infix_postfix_meta_operator). /me waits for test to finish... twiddles thumbs... 22:53
have to do some profiling, perhaps add some memoization... it seems things might be slower now. perhaps the seemingly increased use of complex lookaheads. 22:55
need to get parameterized classes working. they seem the p6 mechanism for declarative modules, eg, one which says eqn(F = m a); and leaves it up to the parameter how to interpret this declaration. 23:01
mncharity TimToady: (9) in statement, <statement_mod_loop> and _cond are followed by EXPR calls... but they already have a <modifier_expr> built into them. typo? 23:18
mncharity TimToady: (10) should circumfix:sigil be '<sigil>+'? t/data_types/hash.t has a '@%(...)'. 23:37
syle anyone got any docs on writing code pertaining to multi-core processers? 23:41
mncharity syle: array ops in p6 are designed with parallelization in mind. and there are threads. but other than that... maybe someone should write an article? :) 23:51
TimToady: (11) in rad_number, the <[ 0..9 a..z A..Z ]> doesn't let one use _ . typo? :2<1_0.1> 23:53

Powered by Cro and the Raku® Programming Language.

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

Thank you!