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.
00:02 Limbic_Region left 00:18 aindilis joined 00:19 rdice left, armagad left 00:22 stevan_ left 00:36 stevan_ joined 00:43 kanru left 00:54 AgeofRuin joined
AgeofRuin can anyone point me in the direction of a good tutorial for perl 00:55
Eevee perl 5? 00:57
or 6
AgeofRuin 6 00:58
Eevee I haven't seen anything very in-depth or tutorial-like online, but there's this: www.oreilly.com/catalog/059600737X/ 00:59
lambdabot Title: O'Reilly Media | Perl 6 and Parrot Essentials
AgeofRuin thanks 01:00
01:00 ead left
Eevee np 01:00
01:04 alanhaggai_ joined 01:06 syle2 left
obra Eevee: that book is..old. and has been freed. there's a copy of it in parrot svn 01:06
Eevee oh seriously
I've just been watching parrot/perl6 from the outside so I can never tell what's up to date 01:07
01:16 Torment joined 01:19 Grrrr left, Grrrr joined 01:20 alanhaggai left 01:27 mj41 left 01:28 yewenbin joined 01:30 Schwern joined 01:32 Jedai left 01:35 quarkcs left 01:38 justatheory joined 01:55 [particle] left 02:04 [particle] joined 02:15 [particle] left 02:16 [particle] joined 02:47 quarkcs joined 02:54 alanhaggai__ joined 02:57 [particle] left 02:58 [particle] joined 03:06 [particle1 joined 03:09 alanhaggai_ left 03:12 [particle2 joined 03:14 [particle3 joined 03:15 [particle] left 03:16 AgeofRuin left 03:21 d4l3k_ joined 03:22 baest left, baest joined 03:23 dalek left, d4l3k_ is now known as dalek 03:31 [particle2 left 03:40 [particle1 left 03:43 Auzon joined 03:49 wknight8111 left 03:51 [particle3 left 03:52 [particle] joined 03:53 alanhaggai_ joined 04:08 alanhaggai__ left 04:16 [particle2 joined 04:20 [particle2 left, [particle2 joined 04:24 Schwern left 04:25 [particle2 left, [particle] left 04:26 [particle] joined 04:30 [particle] left 04:31 [particle] joined 04:32 Psyche^ joined 04:38 [particle1 joined 04:45 Zaba joined 04:49 Patterner left, Psyche^ is now known as Patterner 04:52 alanhaggai_ left 04:59 Zaba_ left 05:04 [particle] left 05:07 alanhaggai joined, Auzon left 05:14 Caelum left 05:30 alanhaggai_ joined 05:38 Caelum joined 05:45 alanhaggai left 06:10 justatheory left 06:15 nipotan is now known as nipotaway 06:21 IllvilJa left 06:23 IllvilJa joined 06:41 Eidolos left 06:49 Eidolos joined 07:08 iblechbot joined 07:10 elmex joined 07:15 jan_______ joined 07:22 jan______ left 07:27 jisom joined, jisom left, alc joined 07:30 quarkcs left 07:32 quarkcs joined 07:46 Zaba_ joined 07:48 alanhaggai_ left 07:52 Zaba__ joined 07:54 quarkcs left, kst left 07:58 Zaba left 08:04 Zaba_ left 08:14 meppl joined 08:28 ruoso joined, alc left 08:50 IllvilJa left 08:56 masak joined 09:08 IllvilJa joined 10:39 wknight8111 joined 10:50 penk left, rdice joined 10:55 Zaba__ is now known as Zaba 11:05 rdice left 11:11 riffraff joined
riffraff hi 11:11
11:15 syle joined 11:23 drfaustus joined 11:24 alc joined 11:40 fridim_ left 12:20 drfaustus left 12:24 masak left 12:26 alc left 12:30 alanhaggai joined 12:35 masak joined 12:44 iblechbot left 12:52 renormalist joined 12:56 alc joined 13:11 Limbic_Region joined
Limbic_Region ?eval sub foo { state $bar = "one"; my $temp = $bar; $bar = "two"; return $temp; } my $msg = foo() ~ foo(); say $msg; 13:13
it has been too long - what is the proper fu to get the evalbot to run p6 code? 13:18
13:19 rdice joined
masak Limbic_Region: see the topic 13:21
either `pugs:`, or `kp6:`, or `rakudo:`, or... 13:22
Limbic_Region danke 13:23
pugs: sub foo { state $bar = "one"; my $temp = $bar; $bar = "two"; return $temp; } my $msg = foo() ~ foo(); say $msg;
exp_evalbot OUTPUT[oneone␤] 13:24
Limbic_Region when did pugs implementation of state variables get broken?
13:28 jhorwitz joined 13:29 eternaleye left 13:46 TJCRI joined 14:00 iblechbot joined 14:14 masak left 14:16 alester joined 14:27 bsb left 14:38 chris2 joined 14:49 yewenbin left, yewenbin joined 14:53 mncharity joined
mncharity TimToady: re S06#Macros "syntax tree form is generally preferred because it allows the parser and debugger to give better error messages. Textual substitution on the other hand tends to yield error messages that are opaque to the user. Syntax trees are also better in general because they are reversible, so things like syntax highlighters can get back to the original language and know which parts of the derived program come from which 14:59
textual substitution can yield good error messages - you just use a string class which remembers where its various characters came from. Similarly, that history permits showing the user the original language and where it came from. To get similar results from syntax trees, also have to teach them to preserve history, else you have a tree, and you know where parts were originally from, but you have no idea how they were massaged into 15:03
now I love tree macros, but find string macros are much maligned. 15:04
;)
wrote such a string class years ago for p5. performance wasn't even horrible. 15:05
hmm, STD.pm regex rules are unchanged from last week. guess I'll move downstream. rx ir and emitter. 15:08
15:19 pmurias joined
pmurias mncharity: it might make sense to turn rules into NFAs instead of turning them into code directly 15:21
mncharity hi pmurias, 15:23
pmurias hi 15:24
mncharity you mean in the current elf parser (STD_red), or in general?
pmurias i'm having doubts if it would really be a good idea
but in an ast transformation stage 15:25
mncharity I was puzzling a few minutes ago how to go forward with parsing. some options include () create a p6 version of STD_red (handwritten or metaprogrammed subs-or-methods); () 15:28
15:28 Schwern joined
mncharity () continue to use STD_red while STD matures; () 15:28
()
() try to massage STD.pm (STD_deconstructed or STD_scrape)? into a form which can be run on a regex engine. 15:29
actually, the "set up for metaprogramming" and "use engine rather than hack" are somewhat orthogonal. 15:30
pmurias metaprogrammed = code-generated
?
;) 15:31
mncharity yeah. STD_deconstructed or STD_scrape -> manageable p6 code.
the equivalent of gimme5 et al in src/perl6
and gimme 15:32
pmurias the first option dosn't seem very good 15:35
i think the choice depends on how long will Larry's effort to bootstrap STD.pm take 15:38
mncharity re first option, has advantages of low development risk (known to work, known to be fast enough), completes bootstrap (ie, so elf could become a cpan module). disadds of lots of manual grunge work.
pmurias do you understand how to implement the longest token stuff? 15:39
mncharity re depends, indeed. and whether the resulting performance permits it to be used for everything, as the day-to-day parser, or just as a bootstrap tool. 15:40
re "longest token stuff", no. I've been waiting for it to work&mature before looking closely at it. 15:41
15:41 kanru joined
mncharity it's still an open question whether the longest token stuff will be a prerequisite for a "good" parse, for some value of good, or whether one can continue fudging it. my impression is one can start making inroads into the pugs t/ while fudging it, or I might prioritize it differently. 15:43
pmurias i read the TDFA paper, but don't full understand what parts of perl6 rules get turned into a DFA and when
TimToady is back, finally...
STD.pm has the changes in, but not checked in because I have my match object contstruction in little bits at the moment 15:44
but I could probably check in STD.pm separately
(was out yesterday at the Dr, but that's overwith now)
mncharity re depends, another issue is how large a role the ruby-ness of STD_red is playing in people not using elf yet. If it was p6, and thus emitted p5, it wouldn't be an issue. but if "elf isn't usefully running against t/ yet, so it's hard to tell what's working" is the bottleneck, then replacing STD_red wouldn't actually help. 15:45
re little bits, :) np. not worth extra effort to buy a day or two. there is other stuff which needs banging on. 15:47
pmurias i think it's the problem of elf not being complete enough 15:48
TimToady I also changed the fate/binding parameterage, so I need to check in changes together, unless people want to see the newest STD.pm just for reference
but I'm probably still the only one actually trying to run STD5_run... 15:49
which probably means the right thing is to just check in a snapshot of where I am regardless of match breakage
[particle1 TimToady++
15:50 [particle1 is now known as [particle]
pugs_svnbot r20316 | lwall++ | [STD] various tweaks suggested by mncharity++ 15:52
r20316 | lwall++ | [gimme et al] new parameter passing regime
r20316 | lwall++ | [cheat] now emits intermediate multi-faking rules as proto tokens
r20316 | lwall++ | [Cursor5] half-refactored match object construction
diff: dev.pugscode.org/changeset/20316
lambdabot Title: Changeset 20316 - Pugs - Trac
TimToady mncharity: I'm sure there are some questions you had about STD that I didn't entirely address yet, but I've forgotten the ones that didn't result in a tweak to STD 15:53
a busy weekend followed by a day under anesthesia will do that to you... 15:54
kolibrie TimToady: I tried running STD5_run once, but have not gotten back to it yet - will need to at some point, but I have no problem with it being broken for a few days 15:55
pugs_svnbot r20317 | putter++ | [elf_e] Non-scalars, @a and %h, in my() and has(), are no longer left uninitialized. But only in elf_e - elf_e_nomoose doesn't do defaults yet.
diff: dev.pugscode.org/changeset/20317
lambdabot Title: Changeset 20317 - Pugs - Trac
mncharity re anesthesia, eep 15:56
TimToady ah, yes, it was regex_assertion:sym<.>, which is already handled by regex_assertion:method
meppl good night 15:57
mncharity good night meppl :) 16:01
meppl ;)
16:01 meppl left
pmurias TimToady: is longest token stuff fully speced out or still being experimented upon? 16:02
16:02 justatheory joined
TimToady it's mostly specced out, though I'm still discovering some interesting holes as I implement 16:02
pugs_svnbot r20318 | putter++ | [elf] EmitRegexYare.pm sketch: expand_backtrack_macros() translated into p6.
diff: dev.pugscode.org/changeset/20318
lambdabot Title: Changeset 20318 - Pugs - Trac
TimToady speaking of which, I also didn't answer the []: question... 16:03
or the "veryify" question--but I think pge is probably wrong there 16:04
*verify, grr
one LTM area that's not specced yet is when a subrule can be a part of a longer token, if the subrule is partly pure and partly impure 16:05
pugs_svnbot r20319 | pmurias++ | [elf] removed .node_name
diff: dev.pugscode.org/changeset/20319
lambdabot Title: Changeset 20319 - Pugs - Trac
16:08 lisppaste3 left
TimToady I think the meaning of []: is clear--you can't backtrack into the [], since it's the previous atom controlled by a bare ':' backtrack controller 16:10
pmurias mncharity: does /misc/pX/Common/yet_another_regex_engine work for you?
TimToady and the q about ' : ' in isolation is just the same backtrack controller applies to previous atom
pmurias mncharity: i mena pass any tests 16:11
TimToady and that's why if: is wrong, because there's no backtracking possible into 'f'
16:14 alc left
mncharity pmurias: why r20319? 16:15
16:15 yewenbin left
mncharity re "yet_another_regex_engine work for you?", yes, on both 5.8.8 and 5.10. not for you? 16:16
TimToady mncharity: did I answer all your q's?
well, all your STD q's, anyway... 16:17
pmurias mncharity: no
mncharity re q's, sorry, got distracted. let's see...
pmurias mncharity: it dosn't work
mncharity re yare doesn't work, ok, that will be third on my stack to explore. 16:18
why r20319?
TimToady shave *my* yak! shave *my* ya! :)
*yak
mncharity lol :)
16:19 pbuetow joined
TimToady take your time really, going off to read perlmonks... 16:19
pmurias if i type "prove t/re_tests.t" i get mostly errors
pasteling "mncharity" at 71.232.7.10 pasted "/usr/bin/prove t/re_tests.t 96.25% okay." (15 lines, 1.3K) at sial.org/pbot/30912 16:34
mncharity pmurias: what does your perl -w Regexp_ModuleA.pm --test output look like?
16:37 renormalist left
mncharity re node_name, that namespace ("CompUnit", etc) is used to describe nodes independently of what package they happen to appear in. Eg, by IRx1_InfoForP5.pm. Though not much code uses it yet. 16:38
16:42 lisppaste3 joined 16:44 gbacon left
mncharity pmurias: or you can use perl -w Regexp_ModuleA.pm --repl to run single cases. 16:48
svn.pugscode.org/pugs/misc/pX/Commo...ine/README 16:49
lambdabot tinyurl.com/6cevls
pugs_svnbot r20320 | putter++ | [elf_e] expand_backtrack_macros() now works. Tweaked p5 prelude regexp helpers. 16:56
r20320 | putter++ | Reverted r20319 - though not yet much used, the node_name names are needed.
diff: dev.pugscode.org/changeset/20320
lambdabot Title: Changeset 20320 - Pugs - Trac
pugs_svnbot r20321 | putter++ | [elf] Reverted r20319 - though not yet much used, the node_name names are needed. r20320 intended to revert it, but didn't. 16:59
diff: dev.pugscode.org/changeset/20321
lambdabot Title: Changeset 20321 - Pugs - Trac
pmurias pugs: class Foo::Bar {};my $foo = Foo::Bar.new();say $foo.WHAT 17:04
exp_evalbot OUTPUT[Foo::Bar␤]
mncharity pmurias: re node_name, if you think it should be renamed, or really think it should be gone, just let me know.
pmurias pugs: class Foo::Bar {};my $foo = Foo::Bar.new();say $foo.WHO
exp_evalbot OUTPUT[*** No such method in class Foo::Bar: "&WHO"␤ at /tmp/1Mh5fVGNA7 line 1, column 48 - line 2, column 1␤]
pmurias what is the short name for an object?
* prototype object 17:05
mncharity: compile "abc" failed: Not a HASH reference at Regexp_ModuleA.pm line 2189 17:06
ruoso wonders if people is following the polymorphism thread in p6-lang
mncharity pmurias: perl -v ?
pmurias 5.8.8 17:07
mncharity very odd
hi ruoso. when you would like to start compiling p6 to smop, just let me know.
ruoso mncharity, I still need to write p6opaque... 17:08
but the compilation could start earlier actually...
you wouldn't be able to test it, tho
but it would already allow writing the p6 types in p6
which is a requirement for SMOP 17:09
17:09 alanhaggai_ joined
ruoso the classes available in the global namespace 17:09
like String
will be the ones implemented in Perl 6
SMOP might use a low-level implementation when you simply do "foo"
17:10 zostay_ joined
ruoso but the Integer type needs to be there... 17:10
17:10 nipotaway is now known as nipotan
pmurias mncharity: wouldn't it be possible to retrieve node_name from .WHO or .WHAT? 17:11
17:14 alanhaggai left
mncharity ruoso: ok. I started on svn.pugscode.org/pugs/misc/elfish_smop/ , but got distracted. Just let me know when it would be good to have it working. 17:16
lambdabot Title: Revision 20321: /misc/elfish_smop 17:17
17:18 barney joined
ruoso mncharity, oh... that one can be working right away... 17:18
it doesn't even depend on p6opaque...
and it could be a way to benchmark how bad SLIME would perform ;) 17:19
mncharity pmurias: re 'wouldn't it be possible to retrieve node_name from', yes, but then, eg, for CompUnit, you would need to trim off the IRx1:: or Whatever::It::Happens::ToBe:: prefix yourself.
17:21 gbacon joined
mncharity ruoso: could you set it up so that given the target code, it actually compiles and runs? that would let the generated code be tested, even when it's "not quite identical, but believed equivalent to" the target. 17:22
ruoso mncharity, actually... I won't be able to do it right now...
real life struggles
but if you like... it won't be that hard making it work... 17:23
mncharity ah. :/ ok. whenever you get a chance.
17:23 zostay left
mncharity since it's main purpose is to help you pursue smop, it's usefulness/interestingness rather depends on your planning to pursue smop. :) 17:25
I'm not sure anyone else is set up to pursue it at the moment.
bummer about not getting funding. 17:26
audreyt had the same problem. :/
ah, TPF. sigh. 17:27
rdice sorry, what? 17:33
ruoso mncharity, I've re-posted SMOP to TPF GC 17:34
rdice made a good job in dealing a new process in the GC
rdice we're trying to make things run better. 17:35
ruoso the proposals will be open for community comments and peer review
rdice and ruoso, I understand you made a new submission.
ruoso rdice, yes... I did...
rdice We were talking about that yesterday.
And we wanted to make sure that it received appropriate public comment.
I have to admit, I try to stay out of the GC's business as much as I can. It is semi-autonomous and has its own rules and regulations. But based on recent experiences they have asked for my help in making some improvements. 17:36
So these things should work their way through the system over the next few months.
ruoso always read garbage collection for GC for a few seconds.... 17:38
17:38 Schwern left
ruoso rdice, it's in much better shape from what I could see... good job... 17:40
rdice Please give 99% of the credit to ambs. :-) I just help him where I can. Wish I could do more, but I have no many different things in TPF that need attention that none of them get as much as what would make things perfect. 17:42
17:42 eternaleye joined, sunnavy_ joined
pugs_svnbot r20322 | putter++ | [STD_red] Unbreak STD_red_run read-eval-print-loop. 17:42
diff: dev.pugscode.org/changeset/20322
lambdabot Title: Changeset 20322 - Pugs - Trac
17:43 sunnavy_ left
[particle] ambs++ rdice-- :P 17:46
17:47 sunnavy_ joined
Eevee so if I were potentially interested in contributing.. which of the myriad of perl 6 interpreters in progress should I be looking at 17:50
17:51 sunnavy_ left
obra That's a good question. Right now, Rakudo has the most momentum 17:53
Though if working on the test suite floats your boat, that's a nice, shared resource 17:54
Eevee rakudo's in the parrot repo and the test suite is largely in pugs, right? 17:55
ruoso later &
17:55 ruoso left
obra correct 17:56
[particle] the test suite is *entirely* in pugs
t/spec/ is the official test suite, and many tests in t/ need to be migrated there 17:57
rdice [particle] Thanks. 17:58
[particle] anytime, rdice :) 17:59
Eevee what's in parrot/languages/perl6/t/spec then? just an older copy of pugs/t/spec? 18:00
[particle] an svn co
check languages/perl 6/Makefile 18:01
*perl6
Eevee oh, ha
how complete is the test suite? 18:03
[particle] it's hard to say, but probably about 25%
we have a GSoC student, Auzon, working this summer on adding ~1000 tests 18:04
mncharity re 25%, I'd guess more like 5%. or less. it's currently more of a "feature exists" checklist, than a "complex feature is handling all the edge cases right" validation suite. 18:10
Eevee ouch 18:11
do any implementations do much not covered by the test suite?
18:11 alinbsp joined
mncharity p6 is a very big and complex language. 18:11
re do much not covered, no, 18:12
Eevee I know, terrible question, but it's hard to get a grasp of where things are
mncharity while not quite test driven development, there has been a focus on avoiding regressions, so features tend to get test cases. 18:13
re grasp, one might look at...
/me struggles to find the smoke test url... 18:16
wee... ok, m19s28.dyndns.org/cgi-bin/pugs-smokeserv.pl will 18:18
lambdabot Title: Pugs Smoke Reports
Eevee intuitive
18:18 elmex left
mncharity give you some idea what is definitely not working. 18:19
Eevee are there smoke tests for rakudo, etc?
mncharity other than that, looking at the tests, and at the p6 modules in ext/ . 18:20
re "smoke tests for rakudo", I don't know. anyone?
18:21 elmex joined
Eevee google's not turning much up except "we need rakudo smoke tests" 18:21
mncharity so that's for pugs. for kp6, which is much more limited, the kp6 t/, and itself (it (is intended to)? self-compile). 18:22
[particle] eevee: auzon will be concentrating on making sure the test suite covers the spec, which is the best way imo
i'm talking to microsoft about using their infrastructure for parrot and rakudo smokes 18:23
mncharity for elf, nothing yet but it's own code (it self compiles) and a list of passing tests.
microsoft, eep
18:24 ispy_ joined 18:25 alinbsp left 18:26 alinbsp joined, alinbsp left
mncharity TimToady: ok, so the residue looks like (1) regex_mod_internal missing nth x etc. (2) regex_metachar:sym<$> needs an alternative to the <before>, so it can match at eos (eor?:). (3) regex_assertion <alpha-[x]> doesn't seem to parse without an additional regex_assertion:ident clause. (4) re regex_assertion:sym<.>, <.ident> is parsed as a method?!? 18:26
Eevee wish all this stuff were more consolidated 18:27
[particle] Eevee: what stuff? the info you're asking about?
mncharity re ext/, that's svn.pugscode.org/pugs/ext/
lambdabot Title: Revision 20322: /ext
[particle] consult the perl 6 wiki, and if it's not there... it's a wiki!
Eevee everything related to perl 6, really
mncharity once upon a time it was mostly running. current mileage may vary.
pmichaud "everything related to perl 6" is pretty big. But I think the general consensus is that we'd like that to be organized on the wiki 18:28
obra Eevee: helping us get things back to a single coherent whole would be higely useful
pmichaud extremely useful, yes
I tend to find the perl6 wiki start page a bit overwhelming, also 18:29
Eevee there is also the opposite problem of taking down everything that's moved or outdated, which is a bit harder
[particle] well, it can be marked for review 18:30
obra starting to make a list would be a reasonable beginning
mncharity www.perlfoundation.org/perl6/index.cgi 18:31
lambdabot Title: Perl 6 / Perl 6
mncharity and feedback would be useful too. there's some concern (well, *I'm* concerned;) that socialtext is currently too weak a wiki engine for the task (eg, no discussion/Talk pages associated with each "article" page). 18:32
ispy_ mncharity: I wouldn't have chosen SocielText, honestly. For that exact purpose. 18:33
pmichaud is there an rss feed for the Perl 6 wiki ?
mncharity s/is/may be/
Eevee haha, did anything ever come of that old offer for someone to write a wiki in perl 6?
ispy_ I have been looking for a project for perl6, but I might be over booking myself.
obra the community needs to outgrow the wiki that was set up for free before it's really worth the effort of replacing it ;) 18:34
mncharity re 'wiki in perl 6', :) not that I know of. elf might actually be strong and fast enough to do it now
ispy_ I am planning on re-writing my news portal in Perl6
18:34 elmex_ joined
mncharity s/to do it/to make it feasible/ 18:34
ispy_ obra: I think we should go ahead and prepare a more scalable solution now, before it becomes a more difficult task later.
pmichaud I see a mythical "we" 18:35
ispy_ haha...
Eevee what is elf exactly 18:36
mncharity obra: re 'the community needs to outgrow the wiki', the problem is growing a wiki community is a very non-trivial and fragile endeavor. so having engine problems... "we'll live on mustard gas for a while, until we out grow it, and then consider moving to oxygen". 18:39
[particle] if rakudo supported sockets, i think it'd be possible to write a wiki engine. actually, with mod_perl6 already working, you won't need sockets 18:40
Juerd Is there a feature matrix for rakudo somewhere? 18:41
[particle] there's a roadmap! 18:42
mncharity even on mediawiki, with a focus and great variety of things intended to help make community easy and attractive, most wikis fail to achieve community critical mass and eventually evaporate.
[particle] svn.perl.org/parrot/trunk/languages/perl 6/\\
grr
svn.perl.org/parrot/trunk/languages...l6/ROADMAP
Juerd [particle]: I'm looking for an itenerary, not a roadmap :)
TimToady mncharity: re (1), I think nth and x are just dups of ** internally, so not necessary, and dubious because they imply a .*? in any case 18:43
Eevee [particle]: why sockets? can always cgi it
Juerd BTW, re wikis, I have a creole wiki grammar 18:44
But I never tried to compile it because I don't know where to start
feather.perl6.nl/~juerd/creole
[particle] Eevee: yes, i was thinking about the whole engine. don't need sockets.
TimToady re (2), I didn't think $ was necessary because you can't have a regex at end-of-file, but then I thought about indirect <$rule>, which can be a string, so yes, it's missing.
18:45 elmex left
TimToady re (3) the intent is that if you're going to do set manipulation you must start with <+ or <- 18:45
Eevee maybe I should give that a try
18:46 elmex_ is now known as elmex
TimToady re (4), the current regex_assertion parsing .ident as a P6 expression, though a postfix would probably be more appropriate there. 18:47
mncharity obra: wrapping up, my one (few?) attempts to edit the wiki bogged down on "what I really want to do is start an out-of-band discussion, not deal with throwing away or substantially changing someone else's nicely edited text". left me with a "don't bother trying that again" feeling, despite a long and strong inclination towards wikis. 18:48
18:48 Auzon joined
mncharity or some such 18:48
[particle] Eevee: i suggest you try mod_perl6 18:49
Eevee oh, wait a minute 18:50
are there any database bindings for perl 6?
pugs_svnbot r20323 | lwall++ | [STD] couple more tweaks from mncharity++ 18:52
diff: dev.pugscode.org/changeset/20323
lambdabot Title: Changeset 20323 - Pugs - Trac
pmichaud mncharity: can the out-of-band discussion go on a mailing list somewhere?
[particle] Eevee: there's no DBI yet
pmichaud mncharity: yes, I agree it's not as nice as having the oob discussion in the same place as the wiki
Eevee not even wrappers for an api? 18:53
that would make a perl 6 wiki a little more problematic
mncharity re (1), looks like svn.perl.org/viewvc/parrot/trunk/t/..._modifiers needs to be tweaked then.
lambdabot Title: 1 [ 6 parrot 1 ] 1 35 Log of /trunk/t/compilers/pge/perl6regex/rx_modifiers 30, tinyurl.com/6rqbtd
[particle] tries to remember if 'system' is implemented in rakudo 18:54
one could *at least* use svn as a wiki backing store with system
pmichaud fwiw, PmWiki uses text files as its database. Works well, for small scales. 18:55
although there are some PmWiki installations with 200K+ pages 18:56
Eevee ouch
mncharity Eevee: re db, elf compiles to p5. :) I've intentionally kept it slightly inconvenient to inline p5, just to avoid sloppiness in doing the bootstrap, but would be happy to change that. :)
might start writing p6 the way you would want to, and then complain to me and rakudo folks when things don't work. :) 18:58
pmichaud yes, exactly 18:59
I'm still a bit slow about responding to things (dayjob), but bug reports and feature requests definitely get higher priority than other things
Eevee well! maybe I will give it a shot 19:01
might just have to go with flatfiles to keep it simple (fsvo "simple")
Juerd BTW, which channel is most appropriate for Rakudo discussion? #perl6 or #parrot? 19:02
[particle] i think flatfiles will work well
TimToady [particle]: there is no system() in p6
[particle] juerd: i prefer #perl6
TimToady: what's the equivalent?
TimToady it is renamed to run() to avoid return value confusion 19:03
[particle] ah, right. thx
mncharity pmichaud: re "go on a mailing list somewhere?" and "not as nice as", that seems a really big barrier. even just requiring logging in and account creation is can be deadly, albeit unavoidable until the community is large enough for 24x7 spam watch. hmm, except for "a few writers are collaborating here on a project" use, vs "the community is maintaining this".
Eevee TimToady: return value will dtrt when cast to boolean?
TimToady documented in S29:1815
Eevee: yes 19:04
Eevee hooray
TimToady success should always be true
19:06 elmex_ joined
pmichaud mncharity: ultimately I agree with you that the wiki as currently implemented isn't exactly conducive to what we're trying to accomplish 19:07
Eevee what does the wiki really need
besides talk pages
pmichaud at this point I think it needs reorganization. It feels like there's too much competing to be on the top level page 19:09
mncharity pmichaud: I don't know that I've ever seen real data, but my fuzzy impression is the issue is people do escalating commitment. With first edits rarely being major. A spelling correction noted in passing, leads to a sentence edit, leads to... etc. Or minor tasks - url mentioned on irc gets added to a page, etc. So one wants that slippery slope as smooth as possible. :)
Eevee: there was talk of perhaps tweaking socialtext to include Talk pages. it might even not be hard. 19:11
re what else does the wiki really need, hmm. I kind of got stuck on the talk issue. drat, don't remember, sorry. 19:14
Eevee I doubt hacking talk pages into any wiki engine would be hard 19:17
mncharity re (3), ah, ok, so svn.perl.org/viewvc/parrot/trunk/t/...iew=markup needs to be tweaked. <alpha-[Jj]>+
lambdabot Title: 1 [ 6 parrot 1 ] 1 35 View of /trunk/t/compilers/pge/perl6regex/rx_subrules 30, tinyurl.com/5ssqaf
19:17 elmex left 19:19 elmex_ is now known as elmex
mncharity TimToady: re (4), "the current regex_assertion parsing .ident as a P6 expression, though a postfix would probably be more appropriate there.", what about <.before \w+?> ? 19:20
it seems . should be ? and ! like, no? 19:21
19:21 ruoso joined 19:22 IllvilJa left
mncharity anyway, I have a workaround. so resolution is not pressing. just flagging it as a potential issue. 19:22
19:25 IllvilJa joined 19:31 aindilis left
pugs_svnbot r20324 | putter++ | [STD_red] Tweaked regex parsing to reflect STD.pm changes. 19:31
diff: dev.pugscode.org/changeset/20324
lambdabot Title: Changeset 20324 - Pugs - Trac
19:31 aindilis joined
mncharity pmurias: re perl -v, what OS? 19:36
pmurias gentoo linux 19:39
pugs_svnbot r20325 | nothingmuch++ | remove overloading from Data::Capture 19:40
diff: dev.pugscode.org/changeset/20325
lambdabot Title: Changeset 20325 - Pugs - Trac
mncharity and -w didn't have any complaints? (5.10 should be making (perhaps bogus) "Variable "$s" is not available" (and "$x") complaints). 19:41
pmurias i'll eat some food, as it's getting cold &
mncharity ok. yeah, I seem to have missed brkfast+lunch. bbiab. :) 19:43
19:45 meppl joined
mncharity with 5.8.8, perl -w Regexp_ModuleA.pm --repl should be -w silent and well behaved. 19:45
pmurias i get a prompt what should i type to check if it works 19:49
?
mncharity if abc is failing, perhaps abc and then a string of xabc ? 19:51
TimToady mncharity: that must be written <.before(/\w+/)>. the . means "call this in method syntax" which happens to have the side effect of not capturing because . is not alphabetic
not that <.before ...> makes any sense anyway... 19:52
but the idea is that if it looks like a method call, it is one. 19:56
pasteling "mncharity" at 71.232.7.10 pasted "perl -w Regexp_ModuleA.pm --repl abc" (9 lines, 288B) at sial.org/pbot/30913
TimToady but yes, that contradicts what S05 says currently. :)
so I guess we can still decide based on whether there's a ( after the ident
pmurias mncharity: have you ci'ed everything? please check sv(n|k) status?
mncharity re "side effect of not capturing", S05, :) ok, np - I left the "( after the ident" hack in std.rb for now. 19:57
pmurias mncharity: checking if it works on feather 19:58
mncharity pmurias: rechecking...
re status, rm -rf'ed, checked out fresh, moved to /tmp, and run as not-me user. 20:00
pugs_svnbot r20326 | lwall++ | [STD] allow both <.foo regex> and <.foo(@args)>
diff: dev.pugscode.org/changeset/20326
lambdabot Title: Changeset 20326 - Pugs - Trac
20:01 armagad joined
pugs_svnbot r20327 | lwall++ | [STD] but also allow <.$indirect()> forms of method call... 20:03
diff: dev.pugscode.org/changeset/20327
lambdabot Title: Changeset 20327 - Pugs - Trac
TimToady now I can picture someone expecting <.foo: 1,2,3> to work the way they expect it to, which says maybe that our current use of : is wrong in assertions... 20:05
mncharity pmurias: that said, Regexp_ModuleA has been observed to cease working if "should have no effect" code reordering is done. a check for that specific case should warn you the perlbug workaround has failed. but I could well believe some other bug is being tickled. p5 support for anon subs seems not entirely robust. and I'm 64 bit to your 32. 20:06
TimToady which would mean we'd need to write <panic: 'message'> with quotes rather than relying on > for final quote 20:09
that seems a bit saner than the current use of : 20:10
pmichaud: see above speculation about <foo: args>
pmurias mncharity: fail on feather too 20:11
mncharity re yare, so there's a development risk for the current effort to add the yet_another_regex_engine core to elf. any flakiness may continue to exist. Long ago I looked at the two 5.10 warnings, but the simpler of the two seemed to be a 5.10 bug.
re feather, I start to say :(, but that should be a :) .
Juerd: after all these years... can I get a feather account? :) 20:12
pmurias mncharity: why a :) ?
* fails
mncharity a replicable problem is a happy problem 20:13
pmurias true
maybe emitting an NFA (with extra bits) wouldn't be a bad idea after all 20:14
pmichaud TimToady: I don't have a problem with <foo: 'args'> 20:15
[particle] finds peace in <foo: 'args'> 20:16
pmichaud that does seem to fit the indirect method syntax somehow, also 20:17
mncharity re alternate core, oh, certainly. I'm just concerned with bootstrap. have working code, in a domain famous for "it's way harder to get this stuff working than you think", so using it. would be nice to use 5.10 reentrancy if its bugs are avoidable, or have an engine coded in p6 which can be compiled down to C, or... etc. 20:18
pmichaud might not be a desirable pun
pmurias s/bad/that bad/
20:18 elmex left
mncharity s/an engine/a vm engine/ 20:19
20:20 Zaba_ joined 20:25 Limbic_Region left
pmurias mncharity: are you familiar with NFAs and DFAs? 20:26
20:33 Zaba left
mncharity re familiar, not really. the hard part is all the optimization games. I've read the odd paper, but no more. actually, my hope/intent is that p6 moves towards providing a general parser. ie, there's intense grammar analysis, a potentially heterogeneous mix of parsing strategies is emitted, but the user doesn't have to be care about parsing theory when writing a grammar. 20:35
no "oh, I have to rewrite this all as (non) left-recursive because the engine is doing x". you should just be able to write a grammar, run it, and if it's not fast enough, ask for hints on where the time is going and how to improve. 20:36
20:37 smtms left 20:43 elmex joined
pmurias mncharity: a subcall for each char would be too slow? 20:43
20:44 barney left
mncharity at runtime, definitely. p5 subcall is ~few hundred us. a C subcall would be faster. but the p5 engine does significantly better. 20:47
200 microseconds means you only get 5000 of them per second. 20:48
pmurias i thought about changing the transitions array of NFA state to a closure 20:49
pugs_svnbot r20328 | lwall++ | [STD] syntax of <panic: "message"> now requires quotes
diff: dev.pugscode.org/changeset/20328
lambdabot Title: Changeset 20328 - Pugs - Trac
mncharity using closures on backends (eg, a hypothetical Common Lisp backend) which can aggressively compile 20:51
20:51 araujo left
mncharity things down could be a win. 20:51
on p5... you would have to profile it.
you're trying to avoid all the object creation of the (current?) STD5 ?
my hope is once the first rx engine in elf is working, it will be easy to experiment with adding additional ones. much of the IR analysis will be shared, and you may be able support the same runtime or compile time apis, and thus can start with partial implementations (either only supporting some features, or only working when some problematic rx constrict doesn't appear). 20:55
pmurias no just thinking about the simplest way to make the NFA none regular,
and cheat around unicode
mncharity ah, ok. 20:56
Juerd If Perl 5's regex engine source was less messy I'd say: look at Perl 5's regex engine for inspiration re cheating around unicode
mncharity hi Juerd. so what's the current recipe for requesting a feather account? 20:57
re p5 engine, I've not see it since the 5.10 changes & cleanup. worth looking at just to appreciate the scale of the task. though my fuzzy recollection is it's actually a bit dumb in some respects. 20:59
Juerd: nm, found it. tnx 21:00
Juerd mncharity: Email me your real name and preferred username
mncharity thanks 21:01
21:04 TJCRI left
mncharity bbl 21:04
21:05 ispy_ left
pmurias mncharity: once you get yare working with elf it should be possible to benchmark other idea's against it 21:06
anyway i should go to sleep now as i don't think clearly enough now ;) & 21:07
21:07 pmurias left 21:15 jhorwitz left
mncharity that's the hope. we'll see. g'night. :) 21:21
pugs_svnbot r20329 | nothingmuch++ | split Capture into ::Overload and normal class, and use it in prepare_binding in Data::Bind
diff: dev.pugscode.org/changeset/20329
lambdabot Title: Changeset 20329 - Pugs - Trac
mncharity eprints.utas.edu.au/644/
lambdabot Title: UTas ePrints - A New General Parser for Extensible Languages
mncharity citeseer.ist.psu.edu/tratt04compiletime.html
lambdabot Title: Compile-time meta-programming in Converge (ResearchIndex)
mncharity random papers
Ian Lewis ("A New General...") is shifting to packrat. 21:24
pugs_svnbot r20330 | nothingmuch++ | split Capture into ::Overload and normal class, and use it in prepare_binding in Data::Bind
diff: dev.pugscode.org/changeset/20330
lambdabot Title: Changeset 20330 - Pugs - Trac
pugs_svnbot r20331 | nothingmuch++ | all_variable_names fixes 21:39
diff: dev.pugscode.org/changeset/20331
lambdabot Title: Changeset 20331 - Pugs - Trac
21:49 rdice left 21:56 eternaleye_ joined 21:57 eternaleye left 22:02 [particle1 joined 22:19 iblechbot left, luqui joined 22:20 [particle] left 22:32 Jamtech joined 22:36 sscaffidi left 22:37 smtms joined 22:40 bsb joined 22:44 Jamtech left 22:48 eternaleye_ left 23:06 luqui left 23:15 luqui joined 23:34 Limbic_Region joined 23:35 syle left 23:37 elmex left 23:49 chris2 left

Powered by Cro and the Raku® Programming Language.

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

Thank you!