Brian Faull <[EMAIL PROTECTED]> writes: > > Aha! I wondered what that class was for (blush) ... > > So did I. It was mind-numbing looking at the API docs for DOMInputSource, > InputSource, and Wrapper4* classes for both... :-\ I'm no OO expert, > but... hmmm...
Yes... At least the Xerces-C team is better at documentation than I have been. Making POD docs for XML-Xerces has been on the TODO list for, well, ever since the project started! The issue I have always had is maintenance of static documentation - or docs would be based on the Xerces-C API, and if it changes or docs need to change. It's one thing if you're documenting your *own* API - if you change the code, you change the docs. But in this case it's monitoring and changing someone elses docs, and that rubs me the wrong way. Unfortunately, while there are excellent automatic documentation tools (like the doxygen system used by Xerces-C), there are no systems (that I'm aware of) that will auto-convert from one API (in C++) to another API (in Perl), unfortunately SWIG only handles wrapping of the code. So, for example, I would want any method in Xerces that requires an XMLCh* (their unicode string), to be documented in Perl as simply taking a scalar (I do a bit under the hood to ensure that you can pass any scalar value, string, int, or float and have it handled properly). So since I don't know how to do automatic wrapping of the docs, I've been trying to generate as many example files as possible that show how to use the API. > > I'll add it and commit it to the SVN repository. You can either grab > > it from there or I can make a dev snapshot tarball. > > Installed and like svn, but don't seem to have the right configuration yet > -- can't snarf the repository. If you would post a tarball at your > convenience, that would be super. Ok, will do. What error do you get when you run: svn co http://svn.apache.org/repos/asf/xml/xerces-p/trunk/ Are you behind a firewall? If so you need to set up your proxy attributes in ~/.subversion. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
