A comment: I realise that, since Marpa is using the *codename{'CODE'} method to resolve the actions, semantic_package, and probably action_object as well, must give a package name that explicitely provide slots for actions in its namespace.
I.e. Marpa does not work with packages that would use the:
use parent 'Parent::Package';
method, letting inheritance do its role (example: the action named myAction in somewhere else), but only with:
use parent 'Parent::Package';
user SUPER;
sub myAction {
# eventually calling super() is enough
}
I have not checked yet with Moose family, but I suppose this is the same thing.
Fine with me, but perhaps to be mentionned in the doc, if not already in.
Thanks / JD.