Had the same problem :) I like the xerces module, but due to a thight
deadline I switched to another module.
But I wil switch back to this one if I have more time to figure the source
code out!
> -----Original Message-----
> From: Jason E. Stewart [mailto:[EMAIL PROTECTED]]
> Sent: maandag 23 juli 2001 17:46
> To: [EMAIL PROTECTED]
> Subject: Re: Documentation
>
>
> "Derek Fountain" <[EMAIL PROTECTED]> writes:
>
> > Just so I know, is there a source of documentation for the
> > Xerces-Perl stuff that I haven't found yet? I'm using the source
> > files and the samples given, plus the XML::Xerces::DOMParse man
> > page. I'm doing SAX work and it's proving a bit hard going!
>
> Sorry Derek,
>
> First, it is really important that Xerces.pm get nice
> documentation. But there are complications that made it a lower
> priority previously.
>
> The Xerces-C API documentation is automatically generated use
> doxygen, and the Xerces.pm file is automatically generated using
> SWIG. So these two don't mesh very well.
>
> In order to get nice useful perl documentation, I'd like to move away
> from auto-generating the interface files with SWIG. This enables me to
> customize each of the methods to be completely perl-like instead of
> many of them now which are very C++-like. This will also enable me to
> add documentation to each class, and each method that won't get blown
> away whenever I regenerate the files.
>
> Help moving over the existing doxygen docs to POD is much appreciated.
>
> jas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
