I would do it but I don't have CVS access for now. The kinds of things
that need to be updated are the following: the dependencies for the
various components (I don't think that this was updated when the
"validation state" object was introduced); the API for the document
handler; etc.
Is there anyone familiar enough with XNI (or who wants to become
familiar enough) that can make these updates?
-AndyC
-------- Message d'origine--------
De: [EMAIL PROTECTED]
Date: jeu. 24/01/2002 16:52
À: [EMAIL PROTECTED]
Cc:
Objet: XNI changes complete
Hi folks,
Just wanted to let everyone know that, as far as I know, the XNI
changes
prompted by our discussion of grammar caching and requests from
James Clark
and Petr Kuzel are done. So just a few more bugs and this will
be ready
for prime-time!
One thing we do need to update though is the XNI manual, so that
it's
properly reflective of all the ways the API has changed
recently. I'll
make sure the release documentation is updated, but this is by
no means a
substitute--especially considering all the work that went in to
preparing
the formal docs in the first place.
Does anyone have the time and inclination to look into this?
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
