Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

context in action functions #11

Closed
rns opened this issue Apr 29, 2015 · 6 comments
Closed

context in action functions #11

rns opened this issue Apr 29, 2015 · 6 comments

Comments

@rns
Copy link
Owner

rns commented Apr 29, 2015

action adverb for LUIF structural rules value of function(...) block end -- it will need context info. Will it be provided via accessors in a separate namespace (like Marpa::R2::Context) or actions will be treated as methods of some inheritable LUIF object?

@jeffreykegler
Copy link
Collaborator

There's lots of stuff I left unspecified about the actions -- for example, the LUIF should treat RHS symbols which occur inside it as values and substitute references to the appropriate child value. And there should be a way of dealing with a RHS like

    X ::= A J A K L A

so that you can refer to the 2nd of the 3 A's. (A:2 is my idea.). Also, I think we should allow the angle bracketed form: <J> and <A:2>. There should be a "raw Lua" way to refer to the RHS values.

And, yes, there should be context accessors of some form. If you want to work this out, feel free to include your own ideas.

@rns
Copy link
Owner Author

rns commented May 3, 2015

I've put my ideas in this manual.md section for your review.

@jeffreykegler
Copy link
Collaborator

I commented in #26. Probably should have done so in this issue, but too
much to remember. :-)

On Sun, May 3, 2015 at 3:39 AM, rns notifications@github.com wrote:

I've put my ideas in this manual.md section
https://github.com/rns/kollos-luif-doc/blob/master/manual.md#defining-semantics-with-action--adverb
for your review.


Reply to this email directly or view it on GitHub
#11 (comment).

@rns
Copy link
Owner Author

rns commented May 4, 2015

Great, this one a candidate for closing. :)

@jeffreykegler
Copy link
Collaborator

I agree, but do not have permission to close issues in this repo.

@rns
Copy link
Owner Author

rns commented May 6, 2015

Ah, yes. Now you have.

@rns rns closed this as completed May 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants