Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2015-07-01

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

All times shown according to UTC.

Time Nick Message
04:14 ronsavage joined #marpa
06:48 ronsavage joined #marpa
07:45 lwa joined #marpa
14:23 koo7 can marpa_g_force_valued really ever fail?
14:54 ilbot3 joined #marpa
14:54 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Pastebin: http://scsys.co.uk:8002/marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today
15:08 sivoais joined #marpa
15:47 jeffreykegler joined #marpa
15:48 jeffreykegler marpa_g_force_valued returns MARPA_ERR_VALUED_IS_LOCKED if a symbol is marked unvalued and its valued status is locked
15:49 jeffreykegler It would be unsafe in any case, in the very real sense that in the future there might be a failure return ...
15:50 jeffreykegler if you assume there will never be one, and you upgrade to a more recent libmarpa, your code won't catch the newly-introduced error
16:22 koo7 i thought it was a deprecated feature
16:22 jeffreykegler It is
16:23 koo7 ah, this reminds me to count from one, i bet i forgot
16:23 jeffreykegler Although I think I used the word "discouraged" instead of deprecated
16:24 koo7 could very well be so
16:25 jeffreykegler The difference being "deprecated" has come to mean "kiss it goodbye fast, because it is going to be yanked away soon!"
16:25 koo7 ok
16:27 jeffreykegler When I say "discouraged" I mean no plans to eliminate it, but please don't use it.
16:27 jeffreykegler ... although I will eliminate it in Kollos, but that won't affect the legacy Libmarpa
18:29 * jeffreykegler give a Kollos update
18:30 jeffreykegler I am working on the grammar rewrite -- a change for Kollos is the much more is done via rewrite, and less in the parse engine ...
18:31 jeffreykegler This will allow the parse engine to become faster and more important smaller ...
18:31 jeffreykegler and smaller means new features can be added.
18:32 jeffreykegler In the rewrite, I am using 3 grammars -- external (x), working (w) and internal (i)
18:32 jeffreykegler Each has a one letter abbreviation, as shown
18:33 jeffreykegler The External grammar is either entered directly via a PLIF (Pure Lua InterFace) or indirectly ...
18:33 jeffreykegler when the LUIF (LUa InterFace) is parsed into PLIF form
18:33 jeffreykegler As the name suggests, it matches the external form closely.
18:35 jeffreykegler The external form never changes, and is to kept for use by those features which must work in terms of the user's original grammar.
18:35 jeffreykegler These features include debugging, tracing, events and semantics.
18:35 jeffreykegler The external rules and symbols are what a LUIF or PLIF user sees.
18:37 jeffreykegler To do the rewrite, I create a working grammar.  This is highly changeable, and the rewrites take place using it.  Once the rewrites are done ...
18:38 jeffreykegler a Libmarpa grammar is created.  Libmarpa's rules and symbols are Kollos's internal rules and symbols.
18:38 jeffreykegler Once the Libmarpa grammar is created, the working grammar is discarded ...
18:39 jeffreykegler all that remains is an internal grammar and an external grammar, and these have links to allow translation back and forth, even on the fly.
18:43 ernimril joined #marpa
19:33 Aria That seems great, jeffreykegler. A nice clean layering
21:20 ernimril joined #marpa
23:08 ronsavage joined #marpa

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