Hey All, Now that 1.5.2_0 is out the door....
Here's my plans: * Stability. I promise that future versions of Xerces.pm will be much more stable with respect to *not requiring* Xerces-C upgrades. All releases in the 1.5.2_X series *will* work with Xerces-C-1.5.2, any versions that I release that require upgrades will only be released in the *experimental* archive under 1.5.3_Y. Xerces-C-1.6.0 is scheduled for released in December, and is scheduled to have full support for XML Schema. When it comes, I will release the latest 1.5.3_Y as 1.6.0_0 and continue with that branch. * Documentation. The next 1.5.2 release of Xerces.pm will have POD documentation for the API. It may not be perfect, but at least it will exist. * Porting. First I want to ensure that the Windows port gets incorporated into the main code base and gets fully supported. Then I plan on reading all Xerces-C configuration information from the config.status file in the Xerces-C source (if you compiled it from source). This will make supporting other platforms (Solaris, HP-UX, ...) much easier. I'll also ask that the Xerces-C team include the config.status in each of there binary releases as well and that way you won't have to build Xerces-C from source in order to get this benefit. * Unicode. Under the hood, Perl uses UTF-8 to store its Unicode while Xerces-C uses UTF-16. This is inefficient becuase whenever one has to talk to the other I must transcode into and out of UTF-16. I'm going to introduce a new class XML::Xerces::XMLString, which is just an array of UTF-16 XMLCh under the hood. All Xerces-C methods that return strings, whether they be char*, XMLCh*, or DOMString will return these objects to Perl. I will support all the appropriate overload operators so that they will work transparently as strings. * Future of DOM. The new IDOM implementation will eventually replace the existing DOM implementation. I will introduce a new pragma 'use XML::Xerces::IDOM;' that exports all IDOM* methods into the DOM* namespace, so that any applications that you have written can immediately switch over to the new implementation without needing to be re-written. At some point (1.6?) I'll stop supporting the old DOM altogether, and just have IDOM export on by default. If you have other needs/desires please write to the list. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
