6.2.11 released! | pugs.blogs.com | pugscode.org | pugs.kwiki.org | paste: sial.org/pbot/perl6
Set by audreyt on 1 February 2006.
dduncan stevan, I was not late, and it seems to have gone well ... will only know if I get the job later 07:50
citing 12 hours ago
ingy Jemplate
nothingmuch chromatic: in case you backlog 08:23
separating to layers is not separating to parts, IMHO 08:24
the standard library and the prelude are not separate parts
they are the same part
except that it's slightly more organized
the linker/compiler/parser/emitter yadda stuff is, again, componentization
the idea here is to simpolify the design, try to make it more reusable, and refactor it a bit 08:25
pugs is already taking this route
i suspect that given organic growth Perl 6 in Perl 6 will also do that
all I'm interested is in helping this process happen by deciding to do this intentionally, together, as a community
instead of by accident, each person on her or his own
since the latter process tends to actually raise the barrier for community participation 08:26
raise programmer burn out
raise the complexity of the whole project from a maintenance and implementation point of view
and so on and so forth
my conjecture is this: organization *MUST* happen
and: we already know what the big parts are going to be
(must happen eventually) 08:27
given these two claims, I think it's safe to say that there is no harm in trying to be a little more prepared for change
making the trial and error process more focused and clean
__END__
nothingmuch meetings-- 13:47
nothingmuch see you all on feb 19th 14:06
gaal, audreyt: FYI you're getting comaint on all my modules in case I die
stevan too
wolverian er, huh?
nothingmuch snowboarding =)
stevan ah
enjoy
wolverian ah :)
have fun
nothingmuch =D 14:07
maybe i'll have netaccess in the airport etc
but probably not there
Juerd faxmodem++ 14:10
nothingmuch: Good luck 14:11
nothingmuch: Break a leg, and no more than that :)
With a broken leg you have a good excuse to:
a) not go to $work
b) hack, hack, hack
:)
gaal so, if we transition to FPS, should this still hold? 16:35
type RuleParser a = GenParser Char RuleState a
since that implies the input is [Char] 16:36
Or does a transition to FPS (therefore?) require deeper hackage in Parsec? 16:37
bsb frames per second? 16:46
you doing macros gaal? 16:47
spinclad purl: FPS? 16:48
gaal bsb: FastPackedString - www.cse.unsw.edu.au/~dons/fps/Data....tring.html
spinclad (FPS is FastPackedString)
gaal Or will we be transitioning to Text.Parser stuff? (Oh great. Monads weren't enough :-) 16:49
integral gaal: deeper parsec hacking I believe 16:51
gaal: My first idea is to investigate if parsec's _interface_ can be put atop Text.Parser.Rule, but maybe not since you have to do a monad -> arrow conversion type thing :-/ 16:52
gaal: you'd probably have to rewrite the GenParser type since your parser will no longer be general enough to parse [a] in general :)
gaal is there any practical use of an [a] parser at all? 16:53
integral Yes in general, in pugs, no, at least not in Pugs.Parser. 16:54
bsb So a normal String is just a list and FPS is a chunk of memory? 16:56
gaal bsb: yes. and "just a list" is lazy.
nothingmuch so, leaving for my aunt's house 19:48
see you at the airport
kolibrie nothingmuch: travel safe 19:49
nothingmuch thanks =)
damnit
wanted to take another movie on the laptop
97.1% complete
i started it yesterday
it's been at 97 since i checked it this morning 19:50
=(
kolibrie oh well

Powered by Cro and the Raku® Programming Language.

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

Thank you!