Hi Daniel,
Little background first. When we develop LSB specification, we
try to divide specification for a given library into multiple sections,
each one representing part of library functionality. The same sections
then map to corresponding header supplied by LSB build environment.
In case of libxml2, we were trying to do that based on the headers, each
one representing the functionality chunk. But while analyzing the
headers we are coming across multiple include loops. E.g. Tree.h is
included in parser.h and parser.h gets included in tree.h through some
include chain (xmlmemory, globals, sax2, parser.h).
How do you suggest we untangle this so that the specification will look
better organized? One option will be to create aggregated includes,
reducing the no. of total include files.
Thanks for your help.
-Rajesh
> -----Original Message-----
> From: Daniel Veillard [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 30, 2005 11:29 AM
> To: Banginwar, Rajesh
> Cc: [email protected]
> Subject: Re: [xml] Which interfaces should be put into LSB?
>
> On Wed, Nov 30, 2005 at 11:24:00AM -0800, Banginwar, Rajesh wrote:
> > Hi Daniel,
> > If all of these headers are meant to be used by application
> > developers, does libXML2 community basically guarantees that these
> > headers will remain functionally similar across versions of libxml2
> > library?
>
> yes.
>
> Daniel
>
> --
> Daniel Veillard | Red Hat http://redhat.com/
> [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit
http://xmlsoft.org/
> http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
_______________________________________________
xml mailing list, project page http://xmlsoft.org/
[email protected]
http://mail.gnome.org/mailman/listinfo/xml
