"Jason E. Stewart" wrote: <snip> > 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.
Agree completely -- no blame from here! > 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). Sounds like a darn good idea. Also sounds like a difficult task, to get auto-documentation to get the semantics of arguments right in such a loosely-typed language as Perl... > 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. ... often more helpful anwyay! The steal-and-modify programming paradigm is much easier than the figure-it-out-yourself technique. :) > > > 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/ svn: RA layer request failed svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request (http://svn.apache.org) > Are you behind a firewall? If so you need to set up your proxy > attributes in ~/.subversion. Already did... am behind firewall -- modified proxy settings accordingly in ~/.subversion/servers which gives the above error. Just tried it without proxy settings, gives "could not connect to server" as expected... On subversion.tigris.org, it suggests using the form $ svn co <URL> <project_name> Or using port 81 rather than 80, or using SSL (https)... also tried those... no luck... Did you (or where did you?) post the tarball? (sorry... not trying to be impatient, no hurry, just couldn't find it...) Thanks again, -brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
