I have another set of API's that differ somewhat from NXP and
Lark.
While we're at it, perhaps we can define a common set of API's for
name resolution? I have a fairly clean API for that that allows
heirarchical name resolution services to be built.
>I would propose seriously that Java be the basis of the first
>cut at an API spec; it is really very pleasingly clean,
>and also has the virtue that ideas can be tested more or less
>instantly because there's running parser code to graft them
>onto. - Tim
I vote for IDL because it's language independent.