Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2016-04-18

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:36 teatime joined #marpa
01:46 teatime m: 0e0.WHAT
01:46 teatime sorry mischan
03:10 ceridwen joined #marpa
03:10 ceridwen joined #marpa
04:02 koo7 joined #marpa
05:36 ronsavage joined #marpa
07:12 ronsavage joined #marpa
08:00 ronsavage jdurand: A heads-up: I've updated SQL page: http://savage.net.au/SQL/.
09:05 koo7 joined #marpa
10:35 rns joined #marpa
11:04 Cheery_ joined #marpa
11:09 shadowpaste joined #marpa
11:16 teatime joined #marpa
12:11 kaare_ joined #marpa
14:43 rns idiosyncrat: re build failures under *BSD, e.g. http://www.cpantesters.org/cpan/report/5a1c4128-053d-11e6-bd2f-67968fb2e322
14:43 rns cp engine/gnu_ac_build/.libs/libmarpa.a xs/libmarpa.a
14:44 rns cp: engine/gnu_ac_build/.libs/libmarpa.a: No such file or directory
14:44 rns *** Error code 1
14:47 rns -- IMHO, looks like make sees updated engine/gnu_ac_build/stamp-h1 even without compilation.
14:49 rns perhaps we need to change engine/gnu_ac_build/stamp-h1 to $(LIBMARPA_IN_BUILD_DIR) per the patch below or add $(TOUCH) $(LIBMARPA_BUILD_DIR)/stamp-h1 before $(MAKE) just as we do with perl_ac_build
14:50 shadowpaste "rns" at 217.168.150.38 pasted "proposed fix for *BSD build failures" (20 lines) at http://fpaste.scsys.co.uk/510844
15:48 rns joined #marpa
21:05 rns left #marpa
22:06 rns joined #marpa
23:04 idiosyncrat_ joined #marpa
23:48 idiosyncrat_ It's early yet, but I want to ask the community about how far to take Marpa::R3 ...
23:49 idiosyncrat_ That is, at some point, I expect we'll do with Marpa::R3 what I did with Marpa::R2 and Marpa::XS before that -- stabilize it and move active Marpa development to a new module
23:50 idiosyncrat_ I plan to add Lua into Marpa at some point, which will make it Turing-complete in a highly efficient way, allowing stuff like events which don't require the overhead of Perl callbacks.
23:51 idiosyncrat_ However, if we add it to Marpa::R3, it means Marpa::R3 becomes dependent on Lua, and there's a lot of stuff that can be done before adding Lua.
23:51 idiosyncrat_ So the question is, stabilize Marpa::R3 before adding Lua, or after?
23:52 idiosyncrat_ We're a good way away from the decision point, but it's important to me when I make the decision to know what the community thinks, and I want to give folks time to think and even change their minds ...
23:52 idiosyncrat_ I know that I'm likely to change my mind about this at least once. :-)
23:54 idiosyncrat_ My current activity is to remove all the methods, arguments, etc., that were "discouraged" in Marpa::R2 from Marpa::R3.

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary