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.
pugs_svnbot r20290 | putter++ | [elf_e] propagate r20289 to the executables. 01:15
diff: dev.pugscode.org/changeset/20290
lambdabot Title: Changeset 20290 - Pugs - Trac
Morasique does anybody know how to call a parent method from within a child class? i'm told it's .SUPER.method(), but it doesn't seem to be working 02:37
mncharity Morasique: which perl6 implementation? 02:42
Morasique mncharity: pugs
Morasique 6.2.13 02:43
mncharity pugs: class A { method m(){say 3}} class B is A{method n(){say SUPER}} B.new.n() 02:43
exp_evalbot OUTPUT[*** No such subroutine: "&SUPER"␤ at /tmp/YXs1yJZOJ8 line 1, column 58-63␤]
mncharity pugs: class A { method m(){say 3}} class B is A{method n(){say self.SUPER}} B.new.n() 02:44
mncharity pugs: class A { method m(){say 3}} class B is A{method n(){say SUPER}} B.new.n() 02:44
exp_evalbot OUTPUT[*** No such subroutine: "&SUPER"␤ at /tmp/PFCi5LK3km line 1, column 58-63␤]
mncharity i don't see many tests for SUPER, and none of that flavor, in t/oo/*.t, which strongly suggests it's not implemented. 02:46
Morasique ok, thanks
mncharity Morasique: if you don't mind me asking, what are you working on? there's another implementation, elf, currently also without SUPER, but to which it would be much more easily added. 02:49
Morasique i'm in an undergraduate group working on a small project, we had to choose a language we didn't already know so we're going with perl 6. we can work around it, it's not a major problem, i just figured it was implemented and i was making a mistake somewhere 02:51
mncharity ah. ok. note that pugs has a lot of rough edges. a common experience is spending a lot of time struggling to work around pugs implementation bugs. and for larger projects, struggling unsuccessfully. 02:54
depending on the project, I'd be hesitant to use it myself. 02:55
Morasique yeah, i imagine this would be pretty bad if we were doing a larger project, but we should be ok for this. thanks 02:59
mncharity np 03:03
pugs_svnbot r20291 | putter++ | [elf_e] Fleshing out regex parsing. 03:40
r20291 | putter++ | [STD_red] same.
diff: dev.pugscode.org/changeset/20291
lambdabot Title: Changeset 20291 - Pugs - Trac
mncharity development path big picture is (1) eat yet_another_regex_engine (node analysis, core, emitters, test suite), and get it working; then (2) contemplate STD.pm hungrily. 03:45
Auzon Does #2 imply a full Perl 6 implementation? 03:46
well, the completion. Contemplating is different from running it :P 03:48
mncharity re full, no. a very great deal of work remains to create a full Perl 6 implementation. but a p6-based version of STD would allow discarding STD_red, and by providing a p6 front end, thus hypothetically make elf a full bootstrap. 03:50
instead of elf just being a backend bootstrap. 03:51
lot of swamp between here and there. 03:52
Auzon I didn't know that elf used Ruby...
mncharity elf uses STD_red to parse code and produce a Match tree. 03:53
Auzon You make this all sound deceptively easy ;) 03:55
mncharity :)
Auzon Well, good luck to you. I hope to play with this stuff once summer begins for me. 03:58
mncharity once you have something which can parse p6, taking that parse tree, and for some small but usable dialect, emitting usably fast code, isn't really enormously difficult. it's that first step which we've historically been stuck on. once one has a usable p6-like implementation, then there's the really big third step, which is 04:01
fleshing it out into a real Perl 6.
Auzon So are you still within parameters for the first step?
mncharity then again, part of that being easy is that other hard pieces have already been done. It would be really depressing if one now needed to write a regex engine from scratch, rather than being able to assimilate a more-or-less working one. 04:03
STD_red remains a work in progress. Basically when elf needs it to be doing better, it gets further attention. It's two biggest current annoyances are needing ";" after "}" which shouldn't need them ("sub f {};"), and broken prefix/postfix operator handling ("$x++"). 04:05
It's also fallen rather out of sync with STD.pm. 04:06
mncharity Hmm. Maybe should do a "}" handling kludge, just so more of the test suite can be run. 04:07
Auzon Is it a fast kludge? :P
mncharity hypothetically, but yes. STD_red payed "manual maintenance and update burden (big, ugly burden)" for "runs fast" and "low development risk". 04:09
Auzon Well, a lack of a semicolon after } is very frequent. But kludges can get ugly. 04:10
mncharity re 'kludges can get ugly', this would just be a simple attempt at lowhanging fruit. eg, /} *\n/ is considered }; . shouldn't break anything in elf, and any tests it helps with are all gravy. 04:14
mncharity end of day. 04:15
Auzon Would this be in STD_red or elf itself?
mncharity STD_red
Auzon ok. Well, good night, if you're leaving.
mncharity well, if you had other questions, I'll stay for a bit. but yes, it's late. 04:16
Auzon No, it's OK. I'm done being curious for tonight :)
mncharity useful to have questions. i'd forgotten about the }; hack idea. 04:17
:)
Auzon Glad I could remind you, then :)
mncharity indeed. thanks.
good night &
lichtkind _a 13:06
PerlJam stevan_: re why I'd like moose.perl.org ... because all other major technologies are available that way: pdl.perl.org, par.perl.org, poe.perl.org, bio.perl.org, etc. So it would be easy to remember whenever I want to point someone at Moose resources. 15:13
(not to mention when I want Moose resources myself :)
stevan_ PerlJam: email sent to [email@hidden.address] lets see what happens :) 15:24
PerlJam: in the meantime, www.iinteractive.com/moose 15:25
lambdabot Title: Moose - A postmodern object system for Perl 5
moritz_ stevan_: I heard that the one of the admins (how should set up a git server) is on vacation, so it might take some time for you to get an answer 15:26
stevan_ moritz_: yeah, I have dealt with them before,they are busy folks,.. I am not holding my breath
Rurick hello every body 16:23
Anyone know how I can open multiple sockets in the same program 16:24
open 4 serves in the same program, maybe with threads or forks? 16:25
allbery_b is this a perl5 question? try #perl
Rurick i am use perl, v5.8.8 16:26
moritz_ here we discuss Perl 6 (which is why the channel is called #perl6 ;-) 16:28
meppl good night 17:29
cognominal_ what is the @INC equivalent in Perl 6? 17:55
moritz_ perhaps @*INC? 17:56
pugs: @*ING
exp_evalbot RESULT[[]]
moritz_ pugs: @*INC
exp_evalbot RESULT[\undef]
moritz_ that's only because evalbot's pugs runs in safe mode 17:57
pugs -e 'say @*INC.perl' # gives you a nice list
TimToady @*INC, if it continues to exist, will likely indicate only the user's private directories 17:58
lambdabot Unknown command, try @list
TimToady pulling things out of the official library will require an official api 17:59
because it more resembles a database query, not a probe of a directory
User629 condition zero scrim anyone 23:28
pugs_svnbot r20292 | putter++ | [elf_e] Grab a copy of yet_another_regex_engine (Regexp_ModuleA.pm). 23:47
diff: dev.pugscode.org/changeset/20292
lambdabot Title: Changeset 20292 - Pugs - Trac
mncharity TimToady: hi. how goes STD.pm? 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!