Here are some of the things which I can respond.
>
> - In the MML API, can Type_Any be a Type_Code?
> * Currently the parser assumes that it can.
I'm not sure what Type_Code means. Is that something you invented?
Didn't we agree to get rid of Type_ ....?
>
> - Since there can be a Rule_None in the Inheritance_Rule, do we need to
> add this to the syntax of MRL?
> * I will need to add this feature to the parser.
Nope. Sionce we changed the way inheritance is specified to
plays_role inherits (x,y,z);
is_like inherist (a,b,c);
If an attribute is not included in any of these lists, then the inheritance
is none.
>
> - Since attributes can have types over those possible in Type_Code, can they
> have a Type_None? How is this done in the MRL syntax? I thought it was
> syntactically incorrect to give an attribute without a ": type" clause.
> * Currently the parser won't let you express a Type_None.
This is related to JK's previous question whether we can defined something
of tyep Any in the MRL specification. I think the answer to that, according
to Pedro is, yes we should support it...but to support it will require
modification of the object system. (Am I correct?) So we cannot support
type Any for the time being.
>
> - How do we encode hooks in the API? Has the API been extended for hooks?
> * ???
I thought you and JK are supposed to work on it. :-)
--Noi