-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
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
so that you can refer to the 2nd of the 3 And, yes, there should be context accessors of some form. If you want to work this out, feel free to include your own ideas. |
I've put my ideas in this manual.md section for your review. |
I commented in #26. Probably should have done so in this issue, but too On Sun, May 3, 2015 at 3:39 AM, rns notifications@github.com wrote:
|
Great, this one a candidate for closing. :) |
I agree, but do not have permission to close issues in this repo. |
Ah, yes. Now you have. |
action
adverb for LUIF structural rules value offunction(...) block end
-- it will need context info. Will it be provided via accessors in a separate namespace (likeMarpa::R2::Context
) or actions will be treated as methods of some inheritable LUIF object?The text was updated successfully, but these errors were encountered: