"::lhs" blessing only allowed if LHS is whitespace and alphanumerics

I got the following error: "::lhs" blessing only allowed if LHS is whitespace and alphanumerics LHS was Does this mean, that the use of underscores in G1 rule names is discouraged? -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To

Re: "::lhs" blessing only allowed if LHS is whitespace and alphanumerics

Am Donnerstag, 26. November 2015 11:13:50 UTC+1 schrieb rns: > > > > On Thu, Nov 26, 2015 at 12:00 PM, Cev Ing > wrote: > >> I got the following error: >> >> "::lhs" blessing only allowed if LHS is whitespace and alphanumerics >>LHS was >> >> Does this mean, that the use

Re: "::lhs" blessing only allowed if LHS is whitespace and alphanumerics

On Thu, Nov 26, 2015 at 12:30 PM, Cev Ing wrote: > Am Donnerstag, 26. November 2015 11:13:50 UTC+1 schrieb rns: >> >> >> >> On Thu, Nov 26, 2015 at 12:00 PM, Cev Ing wrote: >> >>> I got the following error: >>> >>> "::lhs" blessing only allowed if LHS is

Re: "::lhs" blessing only allowed if LHS is whitespace and alphanumerics

Am Donnerstag, 26. November 2015 11:41:37 UTC+1 schrieb rns: > > Don't know exactly. One thing that comes to mind is that _ is then used to > replace spaces in LHS, if any. > As a possible workaround, angle brackets allow using a whitespace in > symbol names, e.g. instead of create_table. >

Global symbol "$EVAL_ERROR" requires explicit package name

When I try the example from the synopsis of Scanless::R, I get the error Global symbol "$EVAL_ERROR" requires explicit package name https://metacpan.org/pod/distribution/Marpa-R2/pod/Scanless/R.pod#Synopsis Is it necessary to import the variable from a Marpa package? -- You received this

Re: Global symbol "$EVAL_ERROR" requires explicit package name

Also, one feature of Marpa is that *all* examples of code are in the test suite -- so they all do actually run in some context. The one for the Scanless::R synopsis is in t/sl_gyn.t. Note that, in the test suite, the context may be some intricate framework required by the testing, but it

Re: Global symbol "$EVAL_ERROR" requires explicit package name

Am Donnerstag, 26. November 2015 17:12:10 UTC+1 schrieb rns: > > > Nope, you an add use English; -- it's a long name for eval's return value. > Ah thanks I got it. Never used the English packages. > If you need a full runnable example, the code from >

Re: Global symbol "$EVAL_ERROR" requires explicit package name

On Thu, Nov 26, 2015 at 6:51 PM, Cev Ing wrote: > > > Am Donnerstag, 26. November 2015 17:12:10 UTC+1 schrieb rns: >> >> >> Nope, you an add use English; -- it's a long name for eval's return value. >> > > Ah thanks I got it. Never used the English packages. > > >> If you need

Re: action => ::lhs

On Thu, Nov 26, 2015 at 7:25 PM, Cev Ing wrote: > I am wondering if it is possible to define a LHS action. I mean something > like this: > > ::= > (CREATE TABLE) identifier ('(') (')' ';') > action => ::lhs > > This should mean call the action with the name of the