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.
Limbic_Region salutations all 00:30
Auzon Hi. 00:33
obra seen fglock 06:28
moritz_ @seen fglock 06:28
lambdabot I saw fglock leaving #perl6 10h 49m 59s ago, and .
xaxxon is it done yet? 09:23
duke perl6'em forever 09:24
clkao o/win 4 09:41
Pox wants his line noise back 11:19
moritz_ injects some grey noise into #perl6
Pox basks 11:20
but seriously, perl6 is way too easy to read for non-adepts
moritz_ you can do nice obfuscation with hyperops 11:21
Pox hehe
even though i have pugs installed
i'm going to use evalbot
to be annoying
?eval for <a b c> -> $a { say $a }
wait
is it in here?
or am i a noob?
moritz_ @list>>.method() takes some time to get used to
lambdabot Unknown command, try @list
moritz_ Pox: the original evalbot is gone, the new one has a different syntax 11:22
Pox ah right
so i'm a noob :P
moritz_ pugs: say "hi, Pox (aka noob;-)"
exp_evalbot OUTPUT[hi, Pox (aka noob;-)␤]
Pox pugs: eval for <a b c> -> $a { say $a }
exp_evalbot OUTPUT[*** ␤ Unexpected "->"␤ expecting operator␤ at /tmp/pmaQwhULdc line 1, column 18␤]
Pox woo i suck 11:23
moritz_ no need for an eval there
pugs: for <a b c> -> $a { say $a }
exp_evalbot OUTPUT[a␤b␤c␤]
Pox yeah
i kinda left the eval from the ?eval
i even suck at IRC 11:24
hmm
moritz_ are you a vacuum cleaner?
Pox ...yes?
moritz_ that explains why you suck so much 11:25
Pox OH
LOL
pugs: say "lo" x 10 ~ "l";
exp_evalbot OUTPUT[lolololololololololol␤]
Pox that string multiplication thing is whacky
moritz_ same as in p5 11:26
Pox really!?
moritz_ only that you use xx in p6 for lists
while you'd use ($item) x $times in p5 to generate a list
Pox eoe
*wow
didn't know that was in perl5
moritz_ eval: print "foo" x 2 11:27
Pox then again, i probably don't use half of perl5
moritz_ though buubot works like that
Pox pugs: say [*] (2,3) 11:29
exp_evalbot OUTPUT[6␤]
Pox weird syntax is great 11:29
Pox pugs: say [**] (2,2,2,2) # 2 tetrate 4 11:30
exp_evalbot OUTPUT[65536␤]
Pox hmmk
i need sleep
long day of perl hacking tomorrow
fglock @tell [particle] re meeting in #parrot yesterday, i couldn't connect from home :( 12:20
lambdabot Consider it noted.
[particle] np, fglock 13:00
lambdabot [particle]: You have 1 new message. '/msg lambdabot @messages' to read it.
ferreira the micro-article on boolean operators is published: www.oreillynet.com/onlamp/blog/2007...or_bo.html 14:07
lambdabot Title: Yet Another Perl 6 Operator: Boolean Operators - O&#039;Reilly ONLamp Blog, tinyurl.com/27rrzs
ferreira it made me wonder about the tests for boolean operators 14:08
I was thinking about how ? (coertion to bool) was tested: svn.pugscode.org/pugs/t/operators/c..._forcers.t
it should not use "ok" but "is $bool_exp, True" and "is $bool_exp, False" 14:09
moritz_ aye
since ok() forces boolean context itself
pugs: say 1 == True 14:10
exp_evalbot OUTPUT[1␤]
moritz_ pugs: say 1 eq True
exp_evalbot OUTPUT[1␤]
moritz_ erm
ferreira moritz_: yep. would you and everyone else agree with that? and think this patch is sane? paste.scsys.co.uk/paste
moritz_ ferreira: give us the real URL please ;) 14:11
ferreira moritz_: that last one is strange
sorry: scsys.co.uk:8001/11414
ispy_ moritz_: so how does this 'examples' directory in pugs work? can we just submit different scripts ( examples ) to it?
moritz_ ispy_: yes, you can 14:12
ispy_: they should work with pugs (but that's no "hard" requirement)
ferreira moritz: the culprit is the convertion from bool to string
ispy_ moritz_: excellent, I've been writing a lot of 50 liners or so for various odds and ends, figured they might be helpful.
ferreira pugs: say ~True
exp_evalbot OUTPUT[1␤]
ferreira pugs: say ~False 14:13
exp_evalbot OUTPUT[␤]
pugs_svn r19188 | pmurias++ | deleted v6-Onion it has been obsoleted by kp6-kp6
moritz_ ferreira: the patch looks fine to me
ferreira do you think I go ahead and commit, or is it better to wait for more eyes to take a look at it? 14:14
moritz_ go and commit it 14:15
anybody who objects is free to correct it or to just revert the patch
pugs_svn r19189 | ferreira++ | r168@dracma: perl | 2007-12-12 12:15:51 -0200 14:16
r19189 | ferreira++ | tests for boolean coertion should use "is"
rhr ferreira: in the article you have [] and {} as true, but S02:1460 says the empty hash is false and I'm pretty sure [] is also 15:09
ferreira rhr: I was wondering about that just now - gonna fix it. Thanks. Double thanks for the reference where to look at 15:11
rhr ferreira++ 15:12
clkao 然後用 binary saerh 15:28
moritz_ ? 15:36
wow, the search for multi byte characters still works in the irc logs: irclog.perlgeek.de/search.pl?channe...C%E7%94%A8 15:37
lambdabot Title: IRC logs - Search, tinyurl.com/34zefn
ispy_ So, since many of you guys in here have been contributing to Perl6 much longer than myself ( obviously ), any guesses as to when P6 will officially be released? Or is that a silly question? :) 15:54
moritz_ ispy_: christmas
ispy_ I know no time table exists, which I believe is good...
ok, so the usual answer...
:)
moritz_ aye ;)
ispy_ great, just wanted to make sure we were on track.
haha..
moritz_ I think 2008 or 2009 15:55
ispy_ sounds good.
moritz_ but it's a tricky questions because not everything is specced yet
ispy_ Yeah I know the deal. 15:56
moritz_ and we don't know how hard the concurrency part will be
to spec, to implement and to test
ispy_ I've been doing a grip load of reading on Perl6 in an attempt to try and catch-up on all the lingo and ideals prior to throwing code on svn ( and helping with existing projects ) so... 15:57
I'm very much looking forward to helping out, I love Perl :)
And I'm surprised because I was very nervous of p6 once I felt I had a solid understanding of p5. 15:58
moritz_ ;)
ispy_ But, after about an hour of messing around with p6 I welcomed many of the changes.
And I realized that I needed to get involved.
moritz_ so you know where to get all the information you need? 15:59
moritz_ and have a pugs commit bit, I hope? 15:59
and you're subscribed to the mailing lists? ;-) 16:00
ispy_ moritz_: yes and yes.
I need to subscribe to perl6-compiler though, I'll do that now.
moritz_ very good
most of the interesting talk happens on p6l, though 16:01
ispy_ I'm going to need my hand held a little, I'll admit. But I'm very eager to contribute, and my code is sound I can assure you.
moritz_: yeah seems to be the most popular list.
[particle] moritz_: i think traffic will shift to p6c now that language design is mostly done, and we're implementing the compilers 16:05
moritz_ [particle]: might be possible, yes 16:06
sproingie is there a freeze date for when design will actually be really really done? 16:16
[particle] yes. 16:17
...but nobody knows when that is.
design doesn't happen before implementation... they happen together 16:18
one influences the other
sproingie yes, but eventually both are finished 16:19
[particle] correct.
since this is an all-volunteer effort, there's no telling when the volunteers will finish
as far as completion percentage goes, larry likes to say that we're done with the first 80%, and well into the second 80% 16:21
pugs_svn r19190 | ferreira++ | r173@dracma: perl | 2007-12-12 15:11:55 -0200 17:12
r19190 | ferreira++ | bool coercion to containers, hashes and undef
fglock from #parrot: <fglock> how about this for a short-term kp6 plan: add a nqp backend and try to self-host on it; and try to reuse code and algorithms from the nqp and perl6 compilers 17:27
Tene Interesting. 17:36
ruoso fglock, yap6 is near being available as another backend ;) 17:40
moritz_ wishes again that #parrot was logged publicly
I followed the discussion, but it would be nice if it was linkable 17:41
Tene It's logged for me. I can make links that I can follow to the discussion. 17:42
;)
moritz_ pugs: my $a; for <1 2> -> { say $a }; say $a; 17:54
exp_evalbot OUTPUT[␤␤␤]
moritz_ pugs: my $a; for <1 2> -> $a { say $a }; say $a; 17:55
exp_evalbot OUTPUT[1␤2␤␤]
pmurias kp6: my $a; for <1 2> -> $a { say $a }; say $a; 18:01
exp_evalbot r19190: OUTPUT[1␤2␤␤]
spinclad looks right 18:03
moritz_ spinclad: it does. I was thinking about www.perlmonks.org/?node_id=656675 18:04
lambdabot Title: Re^3: Duh. 'my' scope in if else blocks. (implicit)
ferreira seen TimToady 18:07
pugs: ~True 18:08
exp_evalbot RESULT["1"]
ferreira pugs: ~False
exp_evalbot RESULT[""]
ferreira hum, that is coherent with the fact that ~True is true and ~False is false 18:09
fglock (#parrot) alternate plan: "fix" the kp6 source code such that it works in nqp
moritz_ but not very symmetric
ferreira moritz: they follow Perl 5 closely: 1==1 returns 1 and 0==1 returns "" - to tell the truth, I heard they return the internal PL_ok and PL_no IIRC 18:11
pmurias fglock: is the plan more oriented towards runing kp6 on parrot or targeting parrot? 18:13
fglock pmurias: both, it would allow kp6 to run both on parrot and Perl 5 (and other backends) 18:14
pmurias if we target the parrot backend seriously shouldn't we target past instead of nqp? 18:17
fglock nqp is Parrot's "MiniPerl6"
it's low-level enough 18:18
moritz_ pmurias: there is no serialization format (yet) for PAST
pmurias nqp
moritz_ pmurias: so you'd trade seriousness for time
gone &
fglock moritz_: :)
pmurias we can use nqp as a serialization format 18:19
once we bootstrap on parrot there is no need to serialize 18:20
fglock nqp is close enough to MiniPerl6, it might even compile kp6 source code
or, we could tweak -Cperl6 18:21
pmurias: do you think this makes sense?
pmurias yes
fglock: i think it's the question which of the two options is less work 18:24
fglock I think -Cnqp makes more sense, because once kp6 gets self-hosted you would want to use Perl 6 syntax 18:25
pmurias fglock: assuming there isn't anything tricky hidden with -Cnqp it seems a better option 18:33
[particle] logs? 18:42
where are the public logs?
is there a bot with that factoid?
pmurias irc.pugscode.org 18:43
[particle] ah. easy!
fglock $ perl script/kp6 -Cperl6 t/kp6/01-tap.t | ~/projetos/parrot-svn/parrot/parrot ~/projetos/parrot-svn/parrot/compilers/nqp/nqp.pbc -- 18:46
I get errors, but it's a start
get to find out what's valid nqp 18:47
I'll create the nqp backend
[particle] where's the source? i can have a look 18:48
er, the source input to parrot
fglock is it Nqp.pm or NQP.pm ?
[particle]: $ perl script/kp6 -Cperl6 t/kp6/01-tap.t
[particle] i'm not sure nqp understands 'module' yet 18:50
pugs_svn r19191 | fglock++ | [kp6] added Emit::Nqp placeholders
[particle] and i'll have to see if it gets & sigil, too
fglock what can we use to start a namespace? 18:51
[particle]: we can tweak the kp6 emitter
pmurias fglock: i would guess it should be NQP? 18:52
[particle] we've always used all lowercase 18:54
but all upper would be fine
hrmm, start a namespace. class?
pugs_svn r19192 | fglock++ | [kp6] fixed Emit::Nqp own namespace and method names
fglock [particle]: see src/KindaPerl6/Visitor/Emit/Nqp.pm 18:55
[particle] oh, nqp does understand module
fglock please rename as appropriate :)
pugs_svn r19193 | ferreira++ | r175@dracma: perl | 2007-12-12 16:57:34 -0200 18:58
r19193 | ferreira++ | basic tests for Bool True and False
[particle] nqp --target=parse x # works (where x contains output from 01-tap.t) 18:59
heck, it even generates PAST 19:00
pugs_svn r19194 | fglock++ | [kp6] added -Cnqp backend 19:01
[particle] No scope found for PAST::Var '&say' # seems like it's saying that lexical lookup failed for this variable 19:02
it's likely that it doesn't know how to process the '&' sigil
hrmm, looks like it should parse & 19:05
s/parse/understand/
fglock the new incantation is: 19:11
$ perl script/kp6 -Cnqp t/kp6/01-tap.t | ~/projetos/parrot-svn/parrot/parrot ~/projetos/parrot-svn/parrot/compilers/nqp/nqp.pbc --
[particle]: I could make kp6 remove & when the var is used in Apply context
[particle] fglock: do it! 19:12
pugs_svn r19195 | fglock++ | [kp6-nqp] removed & sigil when the variable is used in Apply context 19:22
obra fglock: are you likely to be at the lisbon.pm social the first week of January?
fglock obra: sure 19:23
obra Lovely. I'll get to buy you a drink :)
Kaia and I ended up deciding to holiday in portugal the first week of January
we'll be in Porto 31 Dec - 2 Jan. Probably lisbon for a bit after that.
fglock cool :) 19:24
[particle]: it works now, but it emits some syntax messages
pugs_svn r19196 | ferreira++ | r179@dracma: perl | 2007-12-12 17:17:01 -0200 19:25
r19196 | ferreira++ | these tests had wrong anchors - probably to renaming of POD section
r19197 | ferreira++ | r180@dracma: perl | 2007-12-12 17:24:08 -0200
r19197 | ferreira++ | fix todo test: ?| produces Bool, and False does not stringify to 0
[particle] fglock: nqp seems to display the output twice :/ 19:28
fglock I get: error/1..2/ok 1/ ok 2/another error 19:30
fglock home & 19:33
pugs_svn r19198 | ferreira++ | r185@dracma: perl | 2007-12-12 17:36:17 -0200 19:43
r19198 | ferreira++ | added boolean xor infix operator
r19199 | ferreira++ | r186@dracma: perl | 2007-12-12 17:36:40 -0200
r19199 | ferreira++ | added basic tests for boolean infix operators
r19200 | ferreira++ | r187@dracma: perl | 2007-12-12 17:41:50 -0200 19:44
r19200 | ferreira++ | ?&, ?|, ?^ work coercing their arguments to boolean
ferreira rhr: FYI, I fixed the problems with my interpretation of [] and {} as booleans in ONLamp article 19:53
Lyricson 1,8(1,0__1,8/) 22:00
Lyricson 1,8(4o1' '4o1)
Lyricson 1,8(")_(") Pikaaaa Pika Pika chuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu

Powered by Cro and the Raku® Programming Language.

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

Thank you!