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.
rakudo_svn r25779 | coke++ | [codingstd] 01:43
r25779 | coke++ |
r25779 | coke++ | Make the shebang slightly more accurate; these are rakudo files, not raw PIR.
r25779 | coke++ |
r25779 | coke++ | (RT #50802)
pugs_svnbot r19931 | lwall++ | [STD] text extractors no longer use @<more> subnodes; heredoc cleanup 03:07
diff: dev.pugscode.org/changeset/19931
lambdabot Title: Changeset 19931 - Pugs - Trac
meppl good night 03:30
pugs_svnbot r19932 | rhr++ | [STD] typo
diff: dev.pugscode.org/changeset/19932
lambdabot Title: Changeset 19932 - Pugs - Trac
pugs_svnbot r19933 | lwall++ | [gimme5] more backtranslations 07:31
diff: dev.pugscode.org/changeset/19933
lambdabot Title: Changeset 19933 - Pugs - Trac
pugs_svnbot r19934 | putter++ | [misc/red_STD] continuing a first rough transliteration pass through STD.pm. 09:44
diff: dev.pugscode.org/changeset/19934
lambdabot Title: Changeset 19934 - Pugs - Trac
masak I have a comment about S05: 13:19
the list item under "Extensible metasyntax (<...>)" starting "In any case of regex interpolation," seems a bit out of place 13:20
all the other list items talk about what can be part of the <...> syntax
but that one (seemingly) doesn't
hm, S05:1193 I think 13:24
masak also, at "A leading %" under the same section, I'm a bit lost on two accounts. What does it mean to match "like a bare hash", and what does a closure do when it does "whatever it likes"? Some short examples or smartlinks would probably clear it up a bit. 13:28
masak that's S05:1158 13:29
what's the difference between 'eager' and 'greedy' backtracking? 13:32
Gothmog_ wasn't that about returning every possible match, eg a, aa, aaa if you match "aaa" ~~ /a+/? 13:33
masak Gothmog_: yes, I think you're right 13:34
pmurias masak: if you use <$var> var is interpolated as a regex
masak pmurias: yes, it is. 13:37
does that have some connection to base hashes that I'm missing? 13:38
pmurias so if the previous items mentions the ways of interpolating a regex, the next one explains it's semantics 13:39
pmurias S05:924 explains how bare hashes interpolate 13:41
masak ah, ok 13:43
pmurias i think an eager backtracking matches the smallest amount of the atom possible at the first try 13:45
perl -e '"1111" =~ /11*?(1+)/;print "{$1}\n"'
print {11}
err, perl -e '"1111" =~ /11+?(1+)/;print "{$1}\n"' 13:46
* prints
masak so eager backtracking is the opposite of greedy backtracking?
pmurias yes
masak ah, ok 13:47
I can see how they are, but they don't sound opposite :)
instead of 'eager backtracking' I think I would have talked about 'minimal repetitions' 13:48
pmurias masak: the polish translation of programming perl uses the terms "minimalistic" and "maximalistic" quantifiers 14:03
masak ok :) 14:04
I believe that even in English sometimes they occur as synonyms of 'greedy' and 'reluctant', respectively 14:05
pmurias reluctant would be a good replacement for eager 14:13
gnu autotools are annoying 14:14
i want to play with smop a bit but autotools require .deps/repl.Po whatever that is 14:17
mncharity TimToady: random q: in STD.pm's statement_control:if, how does its <EXPR> know to stop before trying to eat the block? 15:59
irclog.perlgeek.de isn't pinging :( (for irclog.perlgeek.de/perl6/today ) 16:01
TimToady mncharity: one of EXPR's standard terminators is ' {' 16:02
bbl & 16:03
mncharity TimToady: re "one of EXPR's standard terminators is ' {'", um, how? There's a terminator:<}> but not {. Somewhere else? 16:05
neat. works if terminator:<{> is added. thanks. :) 16:09
mncharity TimToady: re STD.pm, I don't immediately see a parse for "say 3". subcall provides "say(3)", but parens are required. 17:22
d'oh. term:listop. I had it commented out. knew playing prematurely would squander time debugging. :/ 17:28
pugs_svnbot r19935 | lwall++ | [STD] missing stopper for ending EXPR before block; putter++ 18:24
diff: dev.pugscode.org/changeset/19935
lambdabot Title: Changeset 19935 - Pugs - Trac
diakopter I'm bothered by the varying ways to declare dependencies for modules 18:34
I'm bothered that buildtime (mostly testing) dependencies are not declared separately from runtime and installtime dependencies. 18:36
I'm bothered that, once a module is installed, perl does not know about the buildtime and installtime dependencies, so the dependent module has to detect (test for) the dependencies itself, all over again, in order to fail verbosely. 18:40
pugs_svnbot r19936 | putter++ | [misc/red_STD] took a break from transliteration to slightly increase the set of things correctly parsed. synced commented-out heredoc with STD.pm. 18:45
diff: dev.pugscode.org/changeset/19936
lambdabot Title: Changeset 19936 - Pugs - Trac
diakopter I'm bothered that "optional" dependencies (dependencies that might not be loaded/used) are allowed to exist in a non-plugin fashion. That is, it bothers me that if a certain optional behavior of a module can be dependent on whether another module (or any other system package from the system distribution) is installed, those intricacies have to be handled by the module itself (when the module designer does not plugin-ize the optional be 18:46
mncharity diakopter: long comment warning: I see it end with "does not plugin-ize the optional be" 18:47
diakopter mncharity: you missed only the end of the last word - behavior). 18:48
these thoughts are definitely not fully formed. 18:50
reading about Best Practical's Shipwright triggered these thoughts.
let me restate them from a non-negative tack 18:51
I wish a module's dependencies would always be written declaratively, organized/demarcated by phase. Let's say a module is "installed" in your current working directory. 18:53
scratch that last sentence. Thinking on it more. 18:55
ruoso diakopter, taking that simple... you're just saying that CPAN needed a full-featured package management system, like the debian packaging... 18:57
and besides source-distribution... a binary-distribution would be an important feature...
later & 18:59
diakopter ruoso: I'm not sure. I need to study/read more to be able to talk about this intelligently
pugs_svnbot r19937 | putter++ | misc/red_STD/std.rb: sync with STD.pm r19936. 19:06
diff: dev.pugscode.org/changeset/19937
lambdabot Title: Changeset 19937 - Pugs - Trac
mncharity TimToady: there are a couple of additional observations re STD.pm at the top of misc/red_STD/std.rb.
lichtkind_ Alias_: you here ? 21:11
Alias_ yes 22:00
pugs_svnbot r19938 | putter++ | misc/pX/Common/redsix/redsix: Very lightly dusted. No longer fails to run on the ruby 1.9.0 release, and passes a couple of sanity tests, but make test-redsix still shows pervasive failure. 22:55
r19938 | putter++ | Also added command-line usage help, and fixed the line numbers reported for syntax errors.
r19939 | putter++ | redsix/README: fixed typo.
diff: dev.pugscode.org/changeset/19939
lambdabot Title: Changeset 19939 - Pugs - Trac

Powered by Cro and the Raku® Programming Language.

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

Thank you!