pugs.blogs.com | pugscode.org | pugs.kwiki.org | paste: sial.org/pbot/perl6 | <stevan> Moose... it's the new Camel ":P | .pmc == PPI source filters!
Set by Alias_ on 16 March 2006.
00:13 xinming joined 00:18 rbysamppi joined 00:24 beppu joined 00:42 xinming joined, scook0 joined 00:50 kanru2 is now known as kanru 00:52 Quell joined 00:59 stclare joined 01:06 beppu left 01:14 mkhl joined 01:50 fglock left 02:10 mako132_ joined
stevan audreyt: ping 02:32
audreyt: I think we need to take a serious look at Dylan (if you haven't already) 02:33
02:35 stevan left, stevan joined
audreyt stevan: I have already did 02:36
the day it won ICFP'06 second place.
stevan audreyt: :)
audreyt Dylan, Scala, VB
stevan I just got a book on it in the mail today
audreyt is currently the 3 thing constantly in my mind for AST design :)
excellent
stevan it sounds very much like Perl 6 02:37
static when it can, dynamic when it needs to
audreyt yes 02:39
and "just another lisp with infix syntax"
stevan :)
audreyt I think Dylan is perl6 without advertisement, in a way...
stevan Algol never goes outta style :)
so nothingmuch is using Class::MOP/Moose as a platform for his Perl 6 compilation experiments :) 02:40
audreyt though the Dylan community is... let's say not very vibrant.
stevan: woot! url? 02:41
stevan we need to get you involved once you finish playing with the parser :)
audreyt I've already finished (mostly) :)
stevan audreyt: irc.perl.org #moose mostly right now
audreyt kcool
but where's code? :D
stevan in nothingmuch's head :)
audreyt aw
audreyt thinks nothing exists without a url
stevan he is just getting familiar with the MOP right now
audreyt k. I'd like to see more misc/pX/* experiments :) 02:42
stevan thinks nothingmuch's crainial server might be down for maint right now :)
its pretty late in .il
audreyt k.
I've been tracking Moose releases and internals
stevan we have plans for Moose -> Module::Compile -> Super::Moose 02:43
audreyt: your comments on the TypeConstraint stuff would be much appreciated
that is the part I am least confident about
audreyt well, you don't use container objects
stevan mugwump is playing around with collection containers right now 02:44
but I didnt want to impose that onto everyone in order to use Moose
audreyt I think type constraints belongs to the (say) collection/scalar containers
but it's okay for the class to have a passthru interface 02:45
basically serving as heterogenous hash
that places constraints based onkey
just for performance
the outside interface should remain the same
the only difference is when you take $obj.property as lvalue
stevan nothingmuch and I are working on an Instance sub-protocol, which might allow tighter integration
audreyt excellent
stevan and thoughts of use Moose -strict; have been circulating 02:46
audreyt ponders JFDI and port her $job-Jifty code to Moose 02:47
(and its use of Perl6::Subs to SuperMoose)
stevan the catalyst crew has been doing lots of Mooseing lately
audreyt yes, I've been tracking #catalyst too :)
stevan obra needs to get movin, cause a Moose is much bigger than a Pony :) 02:48
audreyt maybe we'll ship with a Moosey
Moosey in the Sky with Diamonds
stevan :)
obra "Camoony" 02:49
ingy Elk
stevan obra: you will need Perl 6 to write that one :)
hey ingy,.. 02:50
ingy stevan!
stevan I will need a spork tutorial at YAPC
audreyt stevan: so, Super::* is like the namespace for dialects?
stevan audreyt: no, just silliness
audreyt sure 02:51
stevan Moose::Hopped::Up::On::Crack is just as good
audreyt but we're not exactly unknown for take silliness and push them into produciton
stevan :D
obra Moose::::Overdosed::On::Speed::Ecstasy 02:52
stevan obra: you could probably alias that as Moose::Raver
obra Moose::Candy
stevan nothingmuch already claimed Moose::POOP for a Moose ORM 02:53
audreyt ok. I'm now going to Yingge 02:55
# en.wikipedia.org/wiki/Yingge
and paint some Moose porcelain dishes for lambdamoose
stevan :D
in thousands of years people will find them and be like... wtf? 02:56
audreyt *wave* & 02:57
stevan enjoy
03:07 weinig is now known as weinig|sleep 03:12 avar joined 03:25 Quell joined 03:26 Quell joined 03:27 dudleyf joined 03:35 Quell joined 04:51 mjk joined 05:07 coumbes_ joined 05:13 Pete_I joined
meppl guten morgen 05:17
05:18 reZo joined 05:34 azuroth joined
Pete_I hmm. first time i've been greeted in german. g'morning to you too, meppl. 05:37
05:45 Quell joined 05:53 phpError joined
meppl good morning pete 05:57
06:23 ghenry joined 07:28 miyagawa joined 07:37 bsb joined 07:44 larsen joined 08:02 elmex joined 08:03 iblechbot joined 08:16 macroron joined 08:18 wilx joined
svnbot6 r10125 | audreyt++ | * Pugs.Parser: Refactor ruleInConditional into ruleBracketClass 08:20
r10125 | audreyt++ | and use it to implement line-ending statement-terminating blocks:
r10125 | audreyt++ | my &foo := {
r10125 | audreyt++ | say 1;
r10125 | audreyt++ | say 2;
r10125 | audreyt++ | } # Look, no semicolon!
r10125 | audreyt++ | my &bar := {
r10125 | audreyt++ | say 3;
r10125 | audreyt++ | say 4;
r10125 | audreyt++ | } # ditto
r10125 | audreyt++ | See L<S04/Statement-ending blocks> for details. This made parsing
r10125 | audreyt++ | another 5% or so faster...
audreyt bbl again... & 08:22
gaal If you need a mooseword starting with C, there's Caribou. 08:39
08:42 kakos joined 08:56 sockstat joined 09:22 scook0 joined 09:28 drrho joined 09:51 alinbsp joined 10:01 bernhard joined 10:30 chris2 joined 10:43 kioto joined
kioto hi all 10:43
what is the stage of the new perl6 10:50
nothingmuch new?
i thoght there was only one perl 6
or do you mean pugs?
in which case: fun, impressive, and with lots to do
smoke.pugscode.org 10:51
Juerd nothingmuch++ # good summary 10:52
kioto but what is need for a stable version of perl6 10:54
Juerd kioto: needed, or the need?
kioto both 10:55
nothingmuch he need: 10:57
have a nice language
that can be used in a professional environment
without taking a financial risk
and without driving the userbase away
(i'm only addressing stability ;-)
needed: lots... we're still in the poking around stage 10:58
but we think we're closer to the end than to the begining
11:04 kioto left
nothingmuch hmm 11:06
interesting
blog.moertel.com/articles/2006/04/2...in-haskell
11:09 TimToady joined 11:13 iblechbot joined 11:18 KingDiamond joined 11:48 marmic joined 12:00 kane_ joined
pasteling "scw" at 140.112.30.82 pasted "Pugs::Compiler::Rule compile error" (10 lines, 1K) at sial.org/pbot/16966 12:13
scw Any idea? there are both Rule.pm and Rule.pmc under Pugs/Compiler/Rule/ 12:15
It used to choose the .pmc, but not knowing why it doesn't today, weird 12:16
audreyt it takes 12:20
"touch Rule.pmc" 12:21
or
"perl Makefile.PL"
or put pugs/lib to your @INC
svnbot6 r10126 | audreyt++ | * more parsefail fixes... 12:23
scw perl will look at the mtime? 12:26
12:28 Ymmv joined
audreyt yeah, though we get that check disabled for bleadperl (5.9.x) 12:28
for now, try get v6.pm inside your path
or just "touch" it
the Makefile.PL should handle it
clkao audreyt: hey, i need your help 12:29
scw I touched it and passed :)
12:30 elmex joined
audreyt clkao: oh, right. I'm not holding an active title of anything now... 12:30
clkao: you sure I'm eligible for doing that?
clkao yes, for the past of course. (msg plz)
audreyt k
TimToady: parsec complains that 12:42
@moose.map:{'x'}
and
@moose.infix:{'+'}
can't be disambiged. thoughts?
@moose.map: {'x'} # forcing a space would work but a bit draconian 12:44
for now I enumerate the syntactic categs 12:48
12:51 jsiracusa joined, Ymmv joined
cognominal juste posted question about interroperability with Javascript 12:52
It has interestings ramifications 12:53
clkao audreyt: btw, spidermonkey trunk has yeild (almost)
yield, even
audreyt oooh
clkao generator
audreyt yup
12:54 KingDiamond joined
clkao bugzilla.mozilla.org/show_bug.cgi?id=326466 12:54
not totally committed yet, but i think soon
audreyt excellent 12:56
cognominal clkao: e4x has already a nice foreach iterator 12:57
clkao *nod* 12:58
cognominal audreyt: have you read research.microsoft.com/~emeijer/Pap...Sigmod.pdf research.microsoft.com/~emeijer/Papers/XS.pdf 13:06
Too bad this Meijer guy works for the evil empire :) 13:08
audreyt looks at the PDFs 13:09
cognominal I am interested in it because of my xml related stuff in bili 13:10
audreyt I've read the Sigmod one
the XS one I've skimmed 13:11
Juerd audreyt: Be careful! Reading a Microsoft publication, and using the knowledge gained from it in open source software may be illegal ;)
audreyt too bad, I've read most of SPJ's papers ;) 13:14
cognominal SPK and Meijer papers are so good.
xinming No matter what other used... /me is just looking forward perl 6. :-P 13:15
13:17 FurnaceBoy joined
svnbot6 r10127 | audreyt++ | * workaround the "fixity ambig" problem: 13:20
r10127 | audreyt++ | @array.prefix:{'~'}; # method call "prefix:<~>"
r10127 | audreyt++ | @array.map:{'~'}; # method call "map"
r10127 | audreyt++ | by hard coding the list of acceptable category names. 13:21
r10127 | audreyt++ | May need a ruling from @Larry to resolve this.
theorbtwo I suspect the rulling will be something along the lines of "nicely done".
Is it supposed to be possible to add new gramatical catagories? 13:22
audreyt I have... no idea. 13:23
nothingmuch .prefix:{'~'} etc have always bothered me 13:31
they're consistent with the declaration
but i've always had this urge to escape them
i mean, in my head i parsed it as .prefix getting a subref 13:32
even though .prefix is a category i'm used to
Juerd I personally think we're better off with simple namespaces rather than categories, but I haven't really thought that through. 13:35
e.g. prefix::('~')
postcircumfix::(<{ }>) 13:36
Though perhaps the <> can make the () optional, and perhaps we can use {} instead of (). I don't know.
I think that with ::, it looks less magical, and more natural. 13:37
13:37 aufrank joined
Juerd No ambiguity in $foo.prefix:: either 13:37
(afaict)
Juerd doesn't like all the inventions of new syntax, where existing syntax can be used
aufrank Juerd: sorry to jump in late-- what's the proposed new syntax? 13:40
Juerd aufrank: It's not new.
My wording was misleading. 13:41
Or, eh, wrong.
(To avoid more misleading)
aufrank heh
ok, well what are you bother by NOW? (some people, jeez)
Juerd hm? 13:42
I'm not really bothered by the current situation.
Juerd normally doesn't mention most of what he thinks, until he's sure it makes sense. 13:43
But in this case, maybe it could resolve this ambiguity
aufrank I was teasing, I just want to know what alternative to $foo.prefix:: is being discussed
Juerd That *is* the alternative :)
Currently, grammatical categories are written with a single colon. 13:44
aufrank these are the things that are often called adverbs? 13:45
theorbtwo No. 13:46
When you write +$foo, you're really calling a method on $foo.
That method is currently known as prefix:{'+'}.
aufrank ok 13:47
theorbtwo You can also use normal method call syntax, $foo.prefix:{'+'}.
But that could mean that you want to call $foo.prefix with an argument of {'+'}
aufrank is a bair closure following a single colon really an argument? I thought it would have to be wrapped as a capture 13:49
Juerd Okay, if I'm saying things that I have thought about, but of which I'm not sure they make sense, anyway, let's add this related one: 13:50
13:50 Limbic_Region joined
Juerd I think \w+: should be a subcall, where : is an ultimate left paren, that ends at the end of the expression. 13:50
say:+3 # unambiguously say(+3), not (say)+3
theorbtwo I'm not real clear on the current semantics of indirect-object colon. 13:51
audreyt see S03, Invocant marker.
Juerd Doesn't have to clash, as that requires two terms on the LHS
iirc
audreyt but indeed, according to S03, 13:52
@array.map: {4}
is preferred
or
@array.map({4})
but it's not sure whether .map:{4} is always a syntactic category
or can be somehow disambiguated
Juerd I don't want whitespace there :( 13:55
audreyt the thing with @array.infix::<ff> is that it looks like @array.infix::ff
no, neither do I
svnbot6 r10128 | audreyt++ | * Support for .[0], .{foo()}, .<bar> (implicit $_).
r10128 | audreyt++ | * Corrected several test's parsefails, mostly due to
r10128 | audreyt++ | abusing the infinite-backtracking conditional parser.
Juerd The colon is in the place of whitespace, because whitespace wouldn't work.
audreyt right.
aufrank we could have a long colon like the long dot 13:56
Juerd That's what I don't like about the long dot either, for single line uses: there is a character that enables, but then also forces whitespace, whereas something that can replace whitespace feels better
I wish I could think of something better, but I can't
audreyt I think that nicely summarizes my feeling about long dot 13:57
otoh, I think $.foo is an excellent replacement for ./foo, and am looking forward implementing it.
theorbtwo r10128 corrected test parsefails that you decided were the tests being buggy? 13:58
Juerd I think $.foo is nice too. It took a while for me to learn how to read it, because I was too used to the . twigil.
aufrank Juerd: I don't feel strongly one way or the other about the long dot, but one point in its favor is that it allows people to format code in a way that they consider to be more readable 13:59
Juerd Heh, isn't it weird to be "used to" language constructs in a language that according to many people doesn't exist yet? ;)
aufrank and if you just replace whitespace you don't get that, do you?
Juerd aufrank: Of course you DO get that.
13:59 KingDillyDilly joined
Juerd Suppose long dot was just .. (ignoring ranges) 13:59
aufrank I guess I don't understand what you mean by replacing whitespace, then
Juerd $xyzzy.bar(); 14:00
$fooz..bar();
$foo. .bar();
Still lining up.
And IMHO, in a nicer way.
Because long dot now sucks:
$xyzzy.bar();
$fooz. .bar(): # not lining up, so you have to change the PREVIOUS line to use the long dot TOO! 14:01
resulting in:
$xyzzy. .bar();
$fooz. .bar();
Which isn't as nice as my first block of examples.
aufrank now I see
thanks
Juerd But alas, .. is very important.
theorbtwo Hm, how about we make : after a method call be a left paren that will end at ; (without eating the ;)? (Almost Juerd's idea, with a slight reformulation.)
TimToady it's already that, to2
Juerd theorbtwo: I was suggesting it for subcalls. It already exists for method calls :) 14:02
theorbtwo Ah.
TimToady a grammatical category installs two longest tokens, one ending with < and one ending with {
Juerd It's exactly what the $foo.map:{} construct abuses - there's no special :{} postfix afaik
theorbtwo Can we just require space after super-left-paren :? 14:03
TimToady fixing long dot would involve changing the first character to something other than dot.
audreyt TimToady: ok, so @foo.map:{...} works
because there no such longest "map:{" token
TimToady right
audreyt (and there is a third token, ending with french <<)
TimToady right. 14:04
audreyt @moose.elk:{foo}.antler:{bar}
does this work?
"work" as in parsing a
as
@moose.elk({foo}).antler({bar})
instead of
@moose.elk({foo}.antler({bar}))
14:05 hcarty joined, hcarty left
TimToady tokens would be elk :{foo} .antler :{bar} so I believe so. 14:06
(using token to include supertokens)
Juerd Shoes are polished again. 14:07
16:05 < TimToady> fixing long dot would involve changing the first character to something other than dot.
Or changing the range operator ;)
TimToady I think I know which is more important...
Juerd We could have infix ... now that there's no postfix ... anymore ;)
theorbtwo I think so too.
Juerd TimToady: I think be agree too :) 14:08
TimToady and it isn't lining up long dots
Juerd TimToady: See? We agree.
TimToady unfortunately there aren't any convenient ASCII characters left for changing the opening of the long dot.
Juerd I used to maintain a table of taken characters in op and term positions
But then ran out of tuits 14:09
aufrank $foo,.bar
theorbtwo It'd be nice to make middle-dot an any-length dot, but I'm afraid it isn't latin-1, and I can't presently type it anyway.
Juerd aufrank: foo($foo,.bar)
aufrank $fo, .bah
yeah
Juerd aufrank: So won't work.
TimToady well, I have to run off for most of the day.
theorbtwo Have a nice weekend.
Juerd TimToady: Are you still strongly against using $ and @ infix?
aufrank have a good one TT
TimToady As an option, though, a Latin-1 would work along with ". ". 14:10
Juerd (not necessarily related to long dot)
14:10 alinbsp left
TimToady something like ¬ 14:10
ta & 14:11
theorbtwo Oh, ·
That is latin-1.
TimToady something that wouldn't be wanted for infix!!!!
really &
KingDillyDilly audreyt: (continued from 2006-04-27 discussion of PAR), I'm still thinking about search.cpan.org/~smueller/PAR/script/pp even though I don't need to use it. The synopsis seems to be all I need even if I don't understand the examples, so I felt dumb for a minute, but another problem I would have had is figuring out how to install PAR so the examples would work. There's no "use" so it doesn't seem like a module. If it 14:12
Juerd BACKTICK!
audreyt KingDillyDilly: CPAN modules often come with scripts 14:13
Juerd $xyzzy.bar()
audreyt like lwo-download
Juerd $fooz`.bar()
audreyt lwp-download
Juerd $foo` .bar()
audreyt KingDillyDilly: so, install PAR like a normal CPAN module, will get "pp" running on your system
I guess I can make it clearer in the docs.
Juerd: aw. 14:14
Juerd audreyt: Which aw is that? :)
cognominal KingDillyDilly: you questions belong to anotherr channel
theorbtwo ¨ might work, but I suspect is often hard to type || display (that's dead diaresis as a character on it's own).
audreyt Juerd: I'd rather type a full-width dot ;)
Juerd audreyt: is ` so awkwardly placed on your keyboard, or do you hate the glyph? 14:15
aufrank Juerd: not bad
KingDillyDilly audreyt: I have fifty gazillion ideas for improved usability that go beyond what anyone does. Just raising the point because we were discussing it.
aufrank it reads pretty nicely to me
audreyt KingDillyDilly: right. you want a commit bit to PAR?
KingDillyDilly No, that's ok. I think there would be a conflict of interest with my O'Reilly boycott and stuff. 14:16
audreyt (so you can go in and fix the docs, etc.)
I have no idea what PAR has to do with O'Reilly, but sure.
Juerd: I think the multiline
cognominal O'Reilly boycott? do you know that this guy has done a lot for Perl
audreyt $moose`
.blah(3)` 14:17
Juerd audreyt: For multiline, I still want ..., actually.
audreyt .bleh(4)
etc
oh ok. so two forms.
Juerd I keep forgetting that that no longer exists.
I think ".", like "`" is too small to be trailing.
$foo.
.bar
cognominal KingDillyDilly: you should probably be consistent and boycott Perl too
Juerd $foo`
.bar
Little difference, to me
KingDillyDilly cognominal: That belongs on another channel
Juerd (probably depends on font a lot)
Whereas
$foo...
.bar is clearer
audreyt Juerd: at least to my eyes the ".\n" suggests continuation
Juerd To me.
audreyt (but I agree with ...)
Juerd audreyt: Well, to my eyes, ".\n" suggests "full stop" :)
audreyt (and yes, it's highly font dependent.)
oy :) 14:18
Juerd audreyt: Which is why I initially didn't like the change from -> (motion, action) to . (full stop)
audreyt I wonder if "$foo. blah" can be made to mean "$foo.blah"
one-char lookahead
(ok, that idea is even worse.)
Juerd audreyt: How do you feel about having both `<ws>?\. and \.\.\.<ws>\. ? 14:19
Where every sane style guide would prescribe `. for single line, ... . for multiline
audreyt notes that ".:meth" is unclaimed 14:21
I'm fine with "$obj.:meth" meaning same as "$obj.meth" 14:22
that even plays well with the other (dubiously useful) regex-inspired
"$obj.+meth" "$obj.?meth" "$obj.*meth"
Juerd Hmmm 14:23
KingDillyDilly audreyt: "full/path/to/file" can be used instead of just the file name in PAR, right?
audreyt KingDillyDilly: yes.
Juerd audreyt: I'm incredibly unsure about the glyphs, but technically, I like it.
KingDillyDilly ok
Juerd The dozen sided application of : is dangerous
$foo.:foo 14:24
14:24 justatheory joined
Juerd $foo:.foo 14:24
Mean very different things
audreyt then, either "$obj. :moose" can be the long dot
Juerd However, in BOTH, ":" reads "commit".
Hmmm
audreyt or we retain long dot syntax.
yes, in both, ':' reads 'commit', which is why I think it actually works.
Juerd Hmmmm
You rock, audreyt
theorbtwo I don't think it's obvious to people who don't write perl parsers that .: reads commit. 14:25
Juerd I'm no longer unsure about the glyph :)
audreyt curtsies. :)
Juerd theorbtwo: Perl people write Perl regexes, period.
audreyt '.' reads "call"
':' reads "commit"
Juerd theorbtwo: People not used to Perl can't read the language ANYWAY.
Perl is a different language than all those other languages. There's no way to have it syntactically compatible... 14:26
theorbtwo So . reads call (or die), and .: reads call or die.
Juerd Just like Haskell is very different from both C-like languages, and Perl 6
"." reads die?
theorbtwo No, it reads call, and the "or die if the method doesn't exist" is implicit. 14:27
Unlike .?, where it's explicit that you don't die if the method doesn't exit.
exist.
Juerd That's very far fetched.
theorbtwo Then what the heck did you mean by "commit"?
Juerd Do you not know what ":" means in a regex?
audreyt I think you two are in vehement agreement :) 14:28
theorbtwo: yes, it's just like
m/.:/
and
m/./
theorbtwo It means that if you try to backtrack from the right of the colon to the left of the colon, you die.
audreyt means the same thing.
Juerd I think theorbtwo doesn't understand how to read commit, and likes parens too much ;)
theorbtwo: No, it doesn't involve dieing
audreyt I think theorbtwo is parsing things just fine :)
if a method is not found in $foo, the runtime dies. 14:29
but $foo.?method prevents the dying
Juerd theorbtwo: It just means the entire thing left of it is commited, can't change meaning anymore. Focus on the future, not the past.
audreyt and $foo.:method makes explicit that if you can't find the method, please die
which isn't different from $foo.method
Juerd theorbtwo: I don't read "." as die. ":" could read as die, but "." not...
theorbtwo Yes. I was reading . as call, and : as die.
audreyt what Juerd describes is "commit" at the parsing level
which ':' happily puns as well there.
Juerd Maybe "." is the short form of ".:", and ".:" is the real method call op ;)
audreyt heh. 14:30
so, I just implemented this
theorbtwo I'm happy with that, but I'd still prefer .perl shorten it.
;)
Juerd Let's try:
$xyzzy.foo()
$fooz.:foo() 14:31
$foo. :foo()
wfm
theorbtwo WFM too.
Juerd Though there will be people who prefer adding : to the xyzzy too
$xyzzy.:foo()
$fooz. :foo()
$foo. :foo()
fuck
$xyzzy.:foo()
$foo. :foo()
argh!
irssi, stop being helpful please 14:32
Once more
$xyzzy.:foo()
$fooz. :foo()
$foo. :foo()
There :)
theorbtwo Can you put space in .?, .+, and .* as well?
Juerd At least it doesn't involve adding whitespace to the $xzzy call.
theorbtwo: I'd think so.
Can't think of ambiguities
Though that'd create a pair of opposites: ? versus : 14:33
Where in another part of the language, that pair is ? versus !
14:33 Aankhen`` joined
Juerd OTOH, there it is postfix. 14:33
theorbtwo ? boolify vs ! not, you mean? 14:34
Juerd Oh, that too, and that is prefix. Hm
theorbtwo: I meant ($foo!, $bar?)
But indeed, that again stems from ? and !
$xyzzy.foo()
$fooz.!foo()
$foo. !foo()
why? 14:35
why!
$xyzzy.foo()
$fooz.!foo()
$foo. !foo()
audreyt too ambiguous.
Juerd There is no postfix ! in regexes though.
audreyt $foo!foo is private method call.
theorbtwo That must have gotten added when I wasn't paying attention... What is ($foo!, $bar?)
Juerd audreyt: We still have that? Darn :)
audreyt theorbtwo: "is required" and "is optional"
Juerd theorbtwo: The replacement for ($foo, ?$bar)
theorbtwo: positionals default to required, named default to optional. 14:36
aufrank audreyt: is that only in Sigs?
theorbtwo Oh, in a signature.
audreyt aufrank: yes.
Juerd But you can use ? and ! for both if you want.
aufrank if $foo.:bar is regex inspired, do $foo.+bar or $foo.*bar mean anything?
Juerd aufrank: They already mean something. 14:37
aufrank: Not that they're incredibly useful, though
aufrank needs to do another full read through of the syns, apparently
Juerd Larry thinks they may sprout new idioms
theorbtwo .: means "run exactly one", .? means "run if it exists", .* means "run as many as exist", and .+ means "run as many as exist, but at least one". 14:41
KingDillyDilly audreyt: Just to complete my thoughts on this...it's not all that clear that the examples (PAR) must work at the command prompt and won't work in a script without exec or something. I don't think Windows users have a "%" prompt at the command line, and even if they did, personally, I'd make the docs idiot proof. Not a request...just a comment about docs in general.
theorbtwo Do the multiple-running ones have well-defined order and return value? 14:42
Juerd I can see a use for .* and .+ for plugins, perhaps
audreyt KingDillyDilly: if you'd give me your email, I'll send you a commit bit, and you can go in and fix the docs.
svnbot6 r10129 | audreyt++ | * Implement parsing of "extended long dot": 14:43
r10129 | audreyt++ | $foo. +method; # same as $foo.+method
audreyt KingDillyDilly: otherwise, patches welcome on [email@hidden.address]
svnbot6 r10129 | audreyt++ | $foo. *method; # same as $foo.*method
r10129 | audreyt++ | $foo. ?method; # same as $foo.?method
r10129 | audreyt++ | $foo. :method; # same as $foo.:method -- same as $foo.method
r10129 | audreyt++ | (currently the above three is not specially handled yet)
r10129 | audreyt++ | * The old ". ." form is still kept before a ruling is made;
r10129 | audreyt++ | this is just for experimenting with the "feeling" of the syntax.
Juerd $foo does PluginA does PluginB does PluginC;
$foo.*hook_bar()
audreyt Juerd: so, can I ask your help in writing a p6l post? :) 14:44
Juerd I think you just did :)
audreyt I meta-asked :)
Juerd Cool
my @m_EN = qw(January .. December); 14:45
hmm
(not mine)
audreyt Juerd++ # p6l post 14:46
theorbtwo It would seem that $a..$b should call $a+1 until it gets $b out of it.
audreyt (in advance)
Juerd audreyt: That's unfair, now you force me to help you :D
audreyt if you rollback, I can always -- it back :)
so it's a "let" 14:47
Juerd theorbtwo: Hopefully not, as that would mean an infinite loop for 3..4.5
audreyt: But I used a committing colon in the smiley
audreyt: How can I help you?
theorbtwo Well, unless there already is an infix .. defined on Num and Num, which I should hope there would be.
Or just change that to "until it gets a >= $b" 14:48
Juerd theorbtwo: That ignores .. for strings
theorbtwo: And .. for other nice things that can range, like date objects 14:49
theorbtwo They can define their own infix:<..>
audreyt Juerd: write to p6l and explain the ".." conflict, and propose ".:" as a solution, and ". :" as an extension, and ". +" as an generalization, and coexistence/removal of ". ." as a consideration 14:50
theorbtwo brb
Juerd audreyt: Will do; mind if I quote your line? :)
audreyt please do :)
audreyt feels multisyllabic 14:51
miyagawa: [OT] I'll go ahead and release JSON::Syck, with alexmv's patch that fixes SingleQuote with trailing spaces. 14:52
14:56 haggai_e joined 14:58 turrepurre joined
nothingmuch audreyt: stevan said you wanted to talk about moose stuff? 15:02
audreyt nothingmuch: sorry, a sec 15:09
15:10 manbou joined
Juerd audreyt: Sent 15:15
audreyt: What's wrong with short words? I like short words. Why would you want more parts in a word? :) 15:16
("parts" means "syllables". Too bad it has no single-syllable synonym ;))
KingDillyDilly wishes "atoms" were called "parts" 15:17
in Perlspeak 15:18
audreyt in S02? it's followed by "Molecules"
(granted, maybe a bit too cute.)
KingDillyDilly forever tries to simplify things 15:19
cognominal yea, right, so we can speak of private parts...
nothingmuch i prefer atoms etc
it implies that it doesn't get smaller
audreyt I do feel "Molecules" in S02 is a bit inaccessible :)
Juerd KingDillyDilly: Making things simpler is good.
merlyn quarks? :)
nothingmuch in that these are the truely core, lowest level abstractions for Perl 6 15:20
Juerd (simplifying => making simpler)
cognominal atom, molecule mark a cleart progression. part does not mean anything.
KingDillyDilly Yeah. I just get antsy when I hear yet another new term
nothingmuch Mollecules, otoh, is a bit of a pun
Juerd Esperanto has -er- for parts
audreyt "Lexical Conventions" and "Whitespace and Comments"
15:20 haggai_e left
audreyt is perhaps better headings for the respective S02 secions 15:20
15:21 mako132_ joined
Juerd pano => bread 15:21
audreyt (the first two)
Juerd panero => bread crumb
nothingmuch i thought they implied more, but that's perhaps just my memory inventing meta-meaning for Atoms, Mollecules =)
audreyt nothingmuch: it does that to us, but in S02's case, they didn't discuss more :)
nothingmuch in which case perhaps they were counter productive
Juerd It doesn't do molekulo, molekulero, though. It has atomo :)
nothingmuch and should be "lexical conventions" and "whitespace and comments" =) 15:22
audreyt++
KingDillyDilly++
15:23 simonp joined
audreyt commits to S02 and credits "Wassercrats" 15:23
KingDillyDilly Looks foward to bragging...if only he knew what S02 was 15:24
audreyt lol :)
it's dev.perl.org/perl6/doc/design/syn/S02.html 15:25
merlyn: amen to "environmental" 15:28
maybe "env variables" or even "enveloped variables" is better 15:29
KingDillyDilly I'm still not sure what I did, but don't tell me. It's funnier this way. 15:30
audreyt fun is good :)
15:32 weinig|sleep is now known as weinig|away
audreyt Juerd++ # nice post 15:33
though I was confused for a bit about the POD part
theorbtwo Indeed.
audreyt until I figured out you were talking about
$foo.#(
=head1 NAME
...
):method(...);
which is, well, er, okay. 15:34
Juerd audreyt: It's not something people should ever do :)
theorbtwo Hm, I wonder if #(...) is going to get confusing when I want to start a comment with a parenthetical phrase. Probably not, since I generally write #<ws> anyway, and rarely start things with parentheticals. 15:35
audreyt theorbtwo: and column-1 # is special
Juerd knows lots of people who write # without whitespace
They will hate this.
theorbtwo Oh, I forgot that, audreyt. That's good.
Juerd I write " # ", normally
Where in block formatted code, I try to first space as far as the block goes
audreyt yeah. I wonder if line-started-with-whitespace-then-comment
is similarly special. 15:36
Juerd aoeuaoeu;
audreyt that will allow
if moose.elk {
Juerd aoeuao; # aoeu
audreyt #line 15
blah
}
which reads maybe better. not sure.
Juerd audreyt: I'd like a character that introduces special things
Instead of a word
So that people can always write #\w without any risk 15:37
audreyt you mean like
=!line 15
etc
Juerd #!line would be fine too
audreyt ok... that plays well with #!/usr/local/bin/perl
Juerd It could even generalize the shebang ;)
audreyt syck minds, etc.
I mean, sick minds.
Juerd I'm not very syck minded because I don't like yaml much. 15:38
15:38 simonp is now known as simonp_
Juerd (I like it a lot, just not the whitespace sensitivity that has caused me trouble) 15:38
audreyt you must be sjck minded then
the json subset of yaml does not have whitespace problems
Juerd No language should ever treat whitespace following or preceding \n specially.
audreyt POD does. 15:39
as does many wikis.
Juerd I don't like that either, in theory.
audreyt oh. well. :)
Juerd I would like to indent my paragraphs, under =heads
=head1 foo
Some text here, that isn't code.
=cut 15:40
audreyt I see your point.
it's signed and floating. :)
Juerd I'm used to indent code so much now, I would probably need help to get off it.
Juerd even indents things that aren't flowed paragraphs in e-mail.
Someone asked my why I always indent postal addresses in mail :) 15:41
audreyt heh :)
15:41 simonp_ left
Juerd And was amazed at the answer 15:41
"Unauthorized copying, reproduction, hiring, lending, public performance and broadcasting prohibited." 15:42
What artist would ever want this be done to their work? 15:43
audreyt goes adding Pugs-Hs items under Google-SoC ideas page
Juerd Hs?
audreyt <- probably getting mentorship in both TPF and Hs.org
Haskell
Pugs-P5 (and -P6) items would be more applicable to the TPF side, I think 15:44
Juerd Are people who go implement Perl 6 using Haskell bi-mentored? ;) 15:45
audreyt maybe ;) 15:46
aufrank is gonna try :) 15:55
Juerd++ # good post! 16:00
clkao what are long dots anyway? what's the different between that and normal $foo.bar()? 16:02
theorbtwo clkao: A long dot takes up more space. 16:04
audreyt clkao: in perl5 you can write 16:05
clkao why do we need them? do we hate ourselves?
audreyt $x {foo}
$obj-> method
$obj ->method
clkao aaah
audreyt it's for alignment
and multilines
$obj->foo(..............)
->bar(...)
etc
theorbtwo Does everybody get a bunch of "Testing with sbc30k" messages when they post to p6l, or is it just me? 16:06
Oh, blast. Juerd just reported that to the list. 16:07
KingDillyDilly Didn't I hear that "long quotes" are something entirely different? Confusing. 16:10
Juerd Perl 5 even allowns $object -> method, which because of the "visual weight" of -> is used by several people I know. 16:11
KingDillyDilly: There are no long quotes.
audreyt KingDillyDilly: I don't think there is a "long quotes", unless you mean << ... >>
KingDillyDilly I thought I heard they were a foriegn language thing. 16:12
audreyt which is known as "Texas quotes"
Juerd: I get that too
the sbc thing
Juerd I still think <> should also be considered Texan. 16:15
As the quote forms aren't <>, but ‹›
KingDillyDilly: Texan «» is <<>>, Texan ¥ is Y 16:16
KingDillyDilly: It is because the people in Texas are unlikely to accept anything other than US-ASCII :) 16:17
They're too consevative and afraid of foreign influence ;)
KingDillyDilly looks up what he's think of in the logs
You don't have to wait for me, you know. Closest I found so far is "wide yen." 16:25
16:25 mako132_ joined
KingDillyDilly Ha...I was thinking of "full-width quotes" as mentioned colabti.de/irclogger/irclogger_log/...-04-26,Wed 16:27
audreyt ah ok :) 16:34
"full width quotes" and "long dots" are probably distinct enough
KingDillyDilly Yeah
16:43 larsen joined
KingDillyDilly fixes bookshelf 16:44
16:44 KingDillyDilly left 16:45 xerox joined 16:52 hexmode joined 16:59 jsiracusa joined 17:07 kanru joined 17:10 kanru joined
xerox Hi. 17:19
Is there anything like a `learn to play (pugs) Perl 6 in small steps today' document somewhere?
audreyt hi. 17:22
svn.openfoundry.org/pugs/docs/ 17:23
in particular, svn.openfoundry.org/pugs/docs/articles/tpr.pod
also, svn.openfoundry.org/pugs/docs/Perl6/Overview/ 17:24
the spec is at dev.perl.org/perl6/doc/synopsis.html
also see examples/ and t/ for sample p6 code.
xerox: a commit bit is on your way. 17:26
paolo at nemail it?
xerox That's my email yes 17:27
audreyt cool. currently the only write-interface is "svn ci", sadly
xerox I don't exactly know svn, but so noted.
audreyt but if you see anything needs improvement, just change the files, and type "svn ci", and that'd be all.
xerox Gotcha. 17:28
audreyt currently we are having some cabal troubles as old cabal does not allow multiple hs-libraries-dir
clkao audreyt: so where were we on data::bind?
audreyt and as such you can see that src/Data/ByteString is symlinked 17:29
I wonder how to cleanly solve this problem without requiring everyone upgrading to new cabal.
clkao: I think we were at the point where hooking Perl6::Bindings and port it to use Filter::Simnple::Compiled
xerox Hmmmm.
audreyt or something like that, would make sense.
clkao but it's using a hand crafted grammar parser.. can we reuse something under misc/Comon? 17:30
xerox audreyt: thank you for the invitation.
audreyt xerox: no prob :) if you feel like testing your svn client, add yourself to AUTHORS
and "svn ci AUTHORS"
xerox I am there hehe.
clkao went to get some beer and got ready for hacking
xerox I did something *time* ago :-)
audreyt indeed you are :) 17:31
yes :)
clkao: the closest is the P::RC grammar in Perl6::Subs
we don't yet have signature grammar in p6 rules syntax 17:32
writing that would be a Very Good First Step (tm)
clkao ok, that requires me learning p6 rules
audreyt it's yaks all the way down.
clkao but that's a healthy yak
xerox I really want to learn something new. Apart from pen-spinning (yay I learnt a trick today!)
clkao audreyt: is the rule spec in repo uptodate? 17:33
audreyt clkao: see the tests in P::G::R
and Pugs-Grammar-MiniPerl6/lib/Pugs/Grammar/MiniPerl6.grammar
rule spec? docs/Perl6/Spec/Rules?
clkao *nod*
audreyt sure is, it's refetched every time you type "perl Makefile.PL" :)
(as we didn't figure out single-file merges)
clkao ya, i mean the source itself
audreyt yes it is.
you can also try it out using either P::C::Rules or Pugs itself (which bridges to PGE) 17:34
(I verified it still works with today's turnk parrot)
xerox: well, make sure that pugs builds in your environment is a good first step... 17:35
xerox Right. 17:36
Makefile.PL doesn't seem to like ghc made in-place.
audreyt nopaste the error? (assuming you have ENV GHC set)
# nopaste = sial.org/pbot/perl6
xerox It just can't find it. 17:37
audreyt export GHC=${HOME}/bin/ghc (bash)
setenv GHC ${HOME}/bin/ghc (csh)
pasteling "xerox" at 151.37.170.44 pasted "Can't find GHC." (9 lines, 381B) at sial.org/pbot/16967 17:39
audreyt hmm 17:41
clkao audreyt: p::g::r? you mean p::c::r? 17:42
audreyt clkao: yes
xerox: what's output of ghc --version? 17:43
xerox $ ghc --version
, version 6.5
audreyt wow
xerox haha
audreyt that's a strange version string.
xerox I'm using something very unstable.
audreyt yeah, we parse version string
xerox ghc-6.5 on i386-darwin-apple, i.e. Mac Intel.
audreyt oooh. I want that 17:44
anyway
xerox (Very pre-alpha build.)
audreyt type "svn up"
and try again
it'd be nice to know that MacIntelGHC can build Pugs.
xerox Yeah.
svnbot6 r10130 | audreyt++ | * xerox reported a GHC 6.5 that doesn't know its own name.
r10130 | audreyt++ | We cope.
xerox hahaha.
17:45 elmex joined
xerox I'd better make install it, I think. 17:45
audreyt dunno if it'd matter.
but sure :)
xerox: btw, I submitted Pugs embedding, datatypes, and debugger/profiler as tasks
pasteling "xerox" at 151.37.170.44 pasted "Buildin'" (55 lines, 2.3K) at sial.org/pbot/16968
audreyt the other 10 will need some thinking to refactor into month-sized chunks
xerox audreyt: great!! 17:46
audreyt "svn up" and try again.
17:46 pmurias joined
pmurias hi 17:46
audreyt pmurias: hi
svnbot6 r10131 | audreyt++ | * not everyone has LWP::Simple...
xerox blesses audreyt 17:47
audreyt becomes an boxed object
xerox Gulp.
audreyt # obscure perl-OO reference
xerox perl Makefil.PL finally worked. 17:48
audreyt yay.
you are on mac intel
ergo, you have a fast cpu
so, "make" :)
xerox Lets time make it.
audreyt (instead of "make unoptimized")
xerox Yeah.
I hope it will not file on -packages
audreyt we rely on STM...
xerox I probably need to pass -L/custom/ghc/ 17:49
But it's a linker thingie, it will show at last.
audreyt yup
and we are using whatever cabal your 6.5 ships
xerox The numbering of the compiled modules is something added by... ?
audreyt GHC 6.5
xerox Oooooh.
Haskell is great.
audreyt good stuff :)
xerox Data.FunctorM is deprected 17:50
*deprecated
Yay :-)
*bang* Duplicate instance declarations.
audreyt ooh, that's new.
nopaste again?
xerox Sure.
audreyt (it builds fine on 6.4.[12]) 17:51
xerox sial.org/pbot/16969
audreyt aha
GHC 6.5's tree is typeable now
whilst 6.4's is not.
this is line 1914 src/Pugs/AST/Internals.hs 17:52
xerox You're pretty damn fast.
audreyt can you add a ghc_version guard there?
#if GHC_VERSION etc
xerox Yep
audreyt waits for xerox's first commit :D 17:53
xerox <= 6.5 is okay as 'etc' ? 17:54
audreyt sure
not sure how pervasive thetypeableness went 17:55
try+error should reveal them
xerox Hmmmm tried 'make' to make sure it fixed it
audreyt cool
svnbot6 r10132 | pmurias++ | Inline-Parrot was copy'ed into Common a week+ ago
xerox sial.org/pbot/16970
audreyt lol's on the line above 17:56
xerox Strange outcome.
audreyt </DrIFT> Do NOT delete! These instances are your friends! -}
xerox Maybe I need a make clean before?
Ah no.
It's me now knowing about CPP. 17:57
s/now/not/
audreyt and the test is on __GLASGOW_HASKELL__
<= 605 17:58
xerox Gotcha.
audreyt I mean, <= 604
xerox Works. /me ^Z the build to svn ci 18:00
audreyt woot 18:01
xerox++
xerox: is it within your priv to add the "Pugs" topic on the SoC wiki? 18:02
xerox Seems worked :-) 18:03
svnbot6 r10133 | Paolo++ | Since GHC 6.5 Tree is typeable, added preprocessor directive to check <= 604.
audreyt yay
xerox I've to ask Isaac, consider it done.
Yeah!
brb
audreyt the fix didn't break 6.4.2
xerox++
it's 2am here, so I'll 1)journal and 2)sleep soon 18:05
see you in ~10 hours :)
xerox Yeah, see ya later!
Thanks much Audrey.
audreyt ditto :)
xerox Argh. 18:18
audreyt mm? 18:19
pasteling "xerox" at 151.37.170.44 pasted "Build error." (11 lines, 881B) at sial.org/pbot/16972
audreyt svn up and try again 18:21
svnbot6 r10134 | audreyt++ | * fix prelude parsefial.
r10133 | Paolo++ | Since GHC 6.5 Tree is typeable, added preprocessor directive to check <= 604.
18:21 Ymmv joined
xerox I remember when you first started pugs, with TaPL... 18:23
Now it's such a mass of code :-)
audreyt or a "mess of code" :)
but yeah :)
xerox Which successfully build on MacIntels :-)
audreyt oooooh!
run some sanity tests?
xerox Sure.
make test? 18:24
audreyt ./pugs t/01-sanity/01-tap.t
xerox Oh.
audreyt but yeah, a "make smoke upload-smoke"
can be fun
pasteling "xerox" at 151.37.170.44 pasted "Sanity cheques." (14 lines, 210B) at sial.org/pbot/16973
audreyt yay, sane.
xerox ^_^
audreyt xerox++
xerox Very pleased. 18:25
audreyt so, where can I get this mysterious MacIntelGHC?
xerox heh!
Wolfgang mailed an url, let me find it.
audreyt I've been debating whether to just give in and buy a MacBookPro17".
xerox I'd advice you to wait a second revision at least
audreyt otoh, they are not exactly cheap.
xerox Everybody is having problems with the first one
audreyt yeah. so maybe wait for MacBookReal15"
FurnaceBoy that would be G4 ;-) 18:26
FurnaceBoy ducks
audreyt nah, it'd be a CureDoo
or something like that
xerox I hope I'll have something like a bunch of money to get some 12" lappie too.
FurnaceBoy they already have a Duo out
FurnaceBoy loves his PB G4 17
xerox I don't know if it's sane, but here it is: www.uni-graz.at/imawww/haskell/ghc-...in.tar.bz2 18:27
audreyt danke sehr.
xerox Yay to big monitors. iMac 20" here, heh.
FurnaceBoy yes, the iMac 20" is nice 18:28
xerox Do you have ghc?
FurnaceBoy I only have PPC Macs. but on.
+no
xerox Oh, kay.
Prelude> primes !! 100000 18:30
599997
(24.10 secs, 1690143048 bytes)
It's: let primes = 2 : 3 : [ n | n <- [5,7..], any ((==0) . (n `mod`)) (takeWhile (\p -> p*p <= n) primes)] 18:31
pugs> [1..10] >>+<< [1..10] 18:34
(2, 4, 6, 8, 10, 12, 14, 16, 18, 20)
xerox remembers! :-)
18:40 cognominal joined 18:42 ruz joined
ruz ?eval 1.say 18:46
evalbot_10082 OUTPUT[1 ] bool::true
ruz fails on the 10127 18:49
18:52 KingDiamond joined, Khisanth joined 18:54 multic joined, multic left
xerox Do statements have to be ended by some special character? 19:03
audreyt ruz: fixed
xerox: normally, semicolon.
audreyt remembers that she should be sleeping
xerox Like 1.say?
audreyt huh? 19:04
svnbot6 r10135 | audreyt++ | * Pugs.Parser: Fix "1.say". ruz++ for reporting that
r10135 | audreyt++ | numbers were considered as whitespace.
xerox pugs> 1.say
audreyt if you are in the pugs shell, and you see
xerox ....>
audreyt ...>
then it means a parsefail
xerox Ah.
audreyt and you can type ^D
ctrl-d
xerox ....> pugs: <stdin>: hGetLine: end of file -- ^D makes it exit. 19:05
audreyt wow. you didn't have readline
in any case
obra audreyt: weren't you going to bed hours ago?
audreyt "svn up ; make"
will fix it
xerox Ah, okay.
audreyt and "1.say" can work again.
obra: yeah.
good night :) &
obra night
xerox Night-o!
audreyt but, but 19:07
I fixed the ....>
so it should now only do line-continuation when it can sensibly be completed
otherwise it parsefails
(the intention of ....> is so you can enter a multiline subroutine etc) 19:08
sleep for real & 19:09
svnbot6 r10136 | audreyt++ | * Pugs.hs: In the interactive shell, only display the 19:10
r10136 | audreyt++ | line-continuing "....>" prompt when we have an
r10136 | audreyt++ | unexpected eof (i.e. when typing something more can
r10136 | audreyt++ | make it parseok again). Otherwise we throw parsefail.
xerox How does one get something readable out of a .pod ? 19:12
ruz perldoc xxxx.pod 19:13
xerox Great.
19:24 dvtoo is now known as dvorak, dvorak is now known as dvtoo 19:28 dvtoo is now known as dvorak 19:29 dvorak is now known as dvtoo
svnbot6 r10137 | audreyt++ | * resurrect JavaScript compilation by adding back the VCode instance. 19:31
19:33 dvtoo joined
svnbot6 r10138 | audreyt++ | * PIL2JS: Work around a subtle parser bug: 19:33
r10138 | audreyt++ | &say.({},1) # fine
r10138 | audreyt++ | &say.({},1).({},1) # parsefail
r10138 | audreyt++ | will investigate tomorrow...
obra "sleep"
clkao does pil2js work again?
xerox I have got a work around for the hs-libraries-dir problem 19:41
But I don't know Perl to fix Makefile.PL
19:44 jserv-- joined
audreyt just describe the fix here and someone will pick up it and hack into Makefile.PL :) 19:44
& 19:46
svnbot6 r10139 | audreyt++ | * More workaround to make JS build pass; however, -BJS still
r10139 | audreyt++ | appears broken, warning about:
r10139 | audreyt++ | uncaught exception: Error: 1 more parameters passed to sub <anonymous in &JS::Root::join> than expected (1)! at <unknown>
r10139 | audreyt++ | More investigation needed.
xerox haha 19:47
You never sleep!
The fix is "simple", instead of using hs-libraries-dir, use ghc-options with "-idir1 -idir2 ...".
Don't pretend you're sleeping, nobody believes you now 19:48
<grin>
19:49 nnunley joined 19:53 axarob joined 20:01 shachaf joined 20:05 dvtoo is now known as dvorak 20:07 dvorak joined
svnbot6 r10140 | audreyt++ | * It turns out Cabal allows for comma-separated values 20:07
r10140 | audreyt++ | in hs-source-dir, so the symlink trick is no longer needed...
xerox Somebody put some sleeping pill in audreyt's drink 20:09
nnunley Sleep committing?
xerox Somehow. 20:10
20:16 borkened joined
svnbot6 r10141 | audreyt++ | * Er, that fix wasn't good at all for GHC 6.4.1. Applied 20:16
r10141 | audreyt++ | xerox++'s suggestion of hand-adding -ithird-party/fps/
r10141 | audreyt++ | to Pugs.cabal.in instead...
xerox ^__^
20:18 aufrank joined 20:26 justatheory joined, aufrank joined
aufrank hey all 20:26
pasteling "aufrank" at 128.151.80.181 pasted "build error with r10140" (24 lines, 2.3K) at sial.org/pbot/16977 20:29
aufrank same thing happens with regular make (as opposed to make unoptimized)
svnbot6 r10142 | pmurias++ | rm _Inline on make clean 20:37
r10142 | pmurias++ | overloading of 0+
pmurias got to pack my computer now, so that's all for today :) (came back from germany tommorow) 20:48
s/tommorow/today 20:49
too much perlguts(1) 20:50
& 20:52
good night
20:56 FurnaceBoy is now known as FB|afk 21:18 dpuu joined 21:19 _SamB_ joined 21:21 _SamB_ is now known as SamB 21:55 kattana_ joined 21:59 FB|afk is now known as FurnaceBoy 22:01 justatheory joined 22:08 larsen joined 22:12 rootcho joined
rootcho hi 22:12
i see declarations like this :
my $domain = ./:host($request, $uri); 22:13
what "./:....." thing mean
does ./ imply some sort of file path
Juerd That was self.
./foo is now $.foo
And :host is now !host 22:14
rootcho aaa i see
Juerd So ./:foo would now be $!foo, if I recall correctly
rootcho hmm..cute ;)
Juerd afk
rootcho when i use hash 22:15
why should i use %hash<key> instead %hash{key} 22:16
why is one prefable than the other
aufrank rootcho: %hash{key} does not automatically stringify key 22:17
it used to in p5, but no longer does in p6
use the %hash<key> form to get single quotes
rootcho i see, thanx 22:18
aufrank use the %hash<<key>> form to get interpolating quotes
rootcho aha
aufrank or use %hash{'key'} to was two keystroke ;)
s/was/waste/
afk
22:27 nothingmuch joined 22:29 drbean_ joined 22:30 rootcho left 22:56 multic joined 23:18 drbean joined 23:24 Eroick joined
Eroick Hi! I check out the perl6 development every so often. How is it comming? 23:24
23:30 Odin-LAP joined 23:34 Ymmv joined 23:38 reZo joined 23:39 pdcawley joined 23:44 aufrank joined 23:53 pdcawley joined
meppl gute nacht 23:55

Powered by Cro and the Raku® Programming Language.

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

Thank you!