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.
meppl good night 01:08
pugs_svnbot r20110 | putter++ | [elf_on_rakudo] -e 'class A {has $.y; method m(){$.y}}' is plausible. -e '3+4' goes boom. 03:35
diff: dev.pugscode.org/changeset/20110
lambdabot Title: Changeset 20110 - Pugs - Trac
mncharity good night &
rakudo_svn r26321 | duff++ | [rakudo] implement auto{increment,decrement} semantics as per S03 05:59
pmurias ruoso: REFERENCE and RELEASE is boilerplate for objects which don't do refcounting? 13:13
ruoso yes...
REFERENCE and RELEASE is just the delegation of the refcounting... not the refcounting per se 13:14
pmurias the same function could be used everywhere right?
instead of a new one doing the same thing being part of the boilerplate? 13:16
ruoso hmmm... maybe... yes... 13:17
pmurias the next thing according to the ROADMAP is lowlevel arrays should they live in lowlevel_array.c? 13:23
ruoso I actually have to rename lowlevel_method.c, I decided to call them smop_s1p_foo.c
like smop_s1p_scalar.c
so array would be smop_s1p_array.c 13:24
pmurias how should _release and _reference functions be called?
ruoso SMOP_REFERENCE(interpreter,value)
SMOP_RELEASE(interpreter,value) 13:25
they are macros defined in include/smop_base.h
pmurias ;) named
ruoso ah
ok..
I need to take an extra look on that to avoid symbol clashing... but you can just have them called smop_s1p_array_reference 13:26
that's safe...
and as they can be static, I don't think they can actually cause symbol clashing... 13:27
pmurias ruoso: what i mean they should be shared between diffrent responder interfaces 13:29
ruoso ah... I see..
well... they are related to the default smop lowlevel implementation... so you could name them smop_lowlevel_generic_reference 13:30
and add it into the smop_lowlevel.h include 13:31
pmurias ok
sm0p.pl is slow :( 13:43
ruoso: why do you end some string literals with '\0'? 13:47
ruoso no reason at all 13:48
just dumbness of my part
pugs_svnbot r20111 | pmurias++ | [smop] 14:00
r20111 | pmurias++ | smop_lowlevel_generic_{release,reference}
r20111 | pmurias++ | array stub
diff: dev.pugscode.org/changeset/20111
lambdabot Title: Changeset 20111 - Pugs - Trac
ruoso pmurias, about sm0p.pl... that's why I've been asking [particle1 to fix the bug in rakudo so i can run it using it... 14:04
pmurias, btw... I'm setting a convention on this lowlevel types symbol names 14:07
it should be SMOP__S1P__Array instead of SMOP__LOWLEVEL__array
pugs_svnbot r20112 | pmurias++ | [smop] fixed according to naming convection 14:12
diff: dev.pugscode.org/changeset/20112
lambdabot Title: Changeset 20112 - Pugs - Trac
ruoso pmurias, you missed the __LOWLEVEL__ part 14:13
it should be __S1P__
because this is just *one* lowlevel implementation
not *the* lowlevel implementation... as there might be many others...
pugs_svnbot r20113 | pmurias++ | [smop] realy fixed the name 14:18
diff: dev.pugscode.org/changeset/20113
lambdabot Title: Changeset 20113 - Pugs - Trac
ruoso pmurias++ 14:30
pmurias ;) 15:02
rakudo_svn r26335 | particle++ | [rakudo] remove accidentally committed test code by duff 17:46
cognominal_ is when cases are supposed to fall thru like in C? 17:50
eternaleye_ cognominal_: I don't believe so; from what I've seen you need to use `next' to do that. 18:07
cognominal_ hum, rakudo falls thru 18:16
that's the missing expression business 18:19
s/expression/exception/
pugs_svnbot r20114 | putter++ | [elf_on_rakudo] +basic exprs. -e 'my $x = (2+3)*4' handled. 18:49
diff: dev.pugscode.org/changeset/20114
lambdabot Title: Changeset 20114 - Pugs - Trac
pugs_svnbot r20115 | putter++ | [elf_on_rakudo] +simple quotes and parameters. 21:38
diff: dev.pugscode.org/changeset/20115
lambdabot Title: Changeset 20115 - Pugs - Trac
mncharity A while back someone pointed to a CPAN module which permitted defining methods on non-blessed references (eg, on ARRAY. so my $a = []; $a->mumble(); can work). Anyone remember what it is called? 21:49
search.cpan.org/~chocolate/autobox-...utobox.pod and search.cpan.org/~stevan/Moose-Autob...Autobox.pm 21:53
lambdabot Title: autobox - call methods on builtin types - search.cpan.org
mncharity I wonder if one could use an autobox-like approach to make lexical overriding of blessed classes possible. So an object blessed Foo might behave as if it were blessed Bar instead (generally Bar will @ISA Foo), permitting lexically scoped extension and overriding of an object's method vocabulary. 22:02
meppl good night 23:31
pugs_svnbot r20116 | putter++ | [elf_on_rakudo] +method calls. self.m(3) .m(3) $x.m(3) 23:35
diff: dev.pugscode.org/changeset/20116
lambdabot Title: Changeset 20116 - Pugs - Trac