pugscode.org/ | nopaste: sial.org/pbot/perl6 | ?eval [~] <m oo se> | We do Haskell, too | > reverse . show $ foldl1 (*) [1..4] | irclog: irc.pugscode.org/
Set by diakopter on 11 July 2007.
hutrecht or not? 00:10
dwave_ is there a perl 6 library specification? 00:17
jjore-m why not, hutrecht? 01:16
hutrecht jjore-m: do you think perl is strong enough to make the new regex the new standard regex? 01:17
jjore-m: (to be adopted by other languages) 01:18
jjore-m uh, how about you see what happens later?
hutrecht jjore-m: i can't wait
jjore-m: i'm curious
jjore-m: the new regex looks very powerful 01:19
jjore-m: it looks revolutionary
jjore-m: i hope it will become a new standard
jjore-m ok, see p5p with the future.pm module.
you need a time machine.
hutrecht what is p5p? 01:20
jjore-m it's the group that produces perl 5.
you know, like 5.10.0 of just a few days ago?
hutrecht probably you're speaking like this because you're not much familiar with the new regex language promised for perl6 01:21
it is quite an improvement, believe me
jjore-m say hutrecht, you've seen parser generators right?
hutrecht jjore-m: yes, i have
jjore-m: why?
jjore-m roughly the new thing looks to me like another powerful parser generator. 01:22
hutrecht jjore-m: yes, but it is still regex
jjore-m it doesn't appear revolutionary to me but does seem to take the state of the common implementation farther. you know, evolutionary. 01:23
hutrecht then call it abrupt evolution
jjore-m er?
hutrecht because regex hasn't evolved much in the past many years
jjore-m say, do you know a pattern language for tree matching other than XPath? 01:24
hutrecht not really
agjal good night 03:38
theorbtwo BTW, regexes have evolved a fair bit in the past few years, it's just that perl 5.8 regexes didn't. Perl 5.10 regexes are now back up to the state of the art, after being stagnant for a while. 10:22
pugs_svn r19240 | ruoso++ | [yap6] Some detailed documentation in README (worth looking), and NEW in the prototype. 15:23
ruoso pmurias, please take a look at the new REAME I just commited... 15:25
I would appreciate an opinion on that
pmurias ruoso: looking 15:30
pugs_svn r19241 | pmurias++ | [yap6] minor english corrections 15:35
pmurias ruoso: the plan is to implement a interpreter in stage 1 perl6? 15:36
ruoso yep...
and do that by extending kp6
Alias_ To create skmp6? 15:37
sorta-kinda-maybe Perl 6?
ruoso heh 15:38
actually, it would be KP6
as it is today
I mean
not
that would be the final interpreter
ruoso the stage 1 would be more like what mini perl 6 is 15:38
exept that it would only have available the native types created by yap6 15:39
pmurias ruoso: what will kp6 generate opcodes for yap6 or c code?
ruoso stage 1 would generate c 15:40
kp6 would interpret perl code
eventually freezing the interpreter state after compilation 15:41
having a "bytecode-like" data to load
pmurias ruoso: the way perl5 does? 15:42
ruoso yep
much like it
pmurias ruoso: you could expand a bit on that part in the README
my first impresion was that stage 2 would also be c code 15:43
and only the last sentence suggests that it is otherwise 15:44
why isn't stage 2 also c code? 15:45
ruoso because the runtime would need to implement a lot of things
like exception model
stack management
but 15:46
in fact, it is possible to translate it to C
even with the optimizations
actually... I don't have the stage 2 completely clear right now, 15:47
as stage 1 is not implemented yet
ruoso KP6 today depends a lot in P5 15:47
the stage 1 needs to implement all that... 15:48
exception model, closures etc
I will only be able to say if stage 2 can or cannot be compiled down to C after stage 1 is implemented
but the natural way would be to work just like p5
pmurias it would avoid needing a c compiler for eval 15:49
ruoso yep... but allowing c compilation would provide JIT compilation for code snippets 15:49
I think we'll have something in between 15:50
pmurias ruoso: i changed the "At first it will be C code" to "Firstly..." 15:51
ruoso I saw it...
pugs_svn r19242 | ruoso++ | [yap6] some more details about stage 2 in README
pmurias is the change correct?
ruoso I'm not sure 15:52
I just spitted the text... without much worry :) any fix is welcome
ruoso lunch & 15:53
pmurias ruoso: i mean is it planed to be something other then C later on? 15:54
clkao /win 8 15:57
pugs_svn r19243 | pmurias++ | [yap6] 2 more minor fixes 15:59
ruoso pmurias, if it's not C, it will be a data structure that the interpreter can load... 16:07
not another language
ruoso getting back to lunch &
enigmus Does pugs support enums? I've tried the examples found in S12 on current pugs but that doesn't seem to work... 20:37
wolverian that's a pretty safe bet it doesn't 20:39
enigmus Probably what the :todo<feature> means in t/oo/enums.t... Thanks. 20:48
Tene pugs_svn: sub infix:<< <+> >> ($a, $b) { $a + $a + $b + $b } 5 <+> 10 21:35
pugs: sub infix:<< <+> >> ($a, $b) { $a + $a + $b + $b } 5 <+> 10
exp_evalbot RESULT[15]
enigmus I'm trying to install v6.pm with 'cpan v6', but I get the following error on 'make test' in v6-0.020/: 23:52
Compilation failed in require at /home/user/.cpan/build/v6-0.020/blib/lib/v6.pm line 65.
It's actually the same error for a bunch of tests. 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!