tclxml-devel

[Tclxml-devel] Switch to SourceForge version of expat?

[Joe E. <jen...@fl...>]

Should we continue to use the tclexpat fork for xml::expat 
and dom::c, or would it be a good idea to switch to the
official expat release hosted at SourceForge?

Unfortunately the two versions are not _entirely_ compatible,
but the required changes (to dom::c anyway) look fairly minor.


--Joe English

  jen...@fl...

Re: [Tclxml-devel] Switch to SourceForge version of expat?

[Steve B. <Ste...@zv...>]

Joe English wrote:
> 
> Should we continue to use the tclexpat fork for xml::expat
> and dom::c, or would it be a good idea to switch to the
> official expat release hosted at SourceForge?

Yes.  My plan was to merge the Ajuba changes into the SF version.

When we release TclXML we should probably include the expat sources
in the distribution (it's not all that big).

> Unfortunately the two versions are not _entirely_ compatible,
> but the required changes (to dom::c anyway) look fairly minor.

dom::c shouldn't even know about (tcl)expat; it should be using the
new C API in TclXML v2.0.  TclXML itself then handles the interface
to the parser class implementation.  That way, dom::c could use
expat, tclparser, tclxerces, xmllib, etc (the latter two would give
you a validating parser).

Cheers,
Steve Ball

-- 
Steve Ball            | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |      XML XSL
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

Re: [Tclxml-devel] Switch to SourceForge version of expat?

[Joe E. <jen...@fl...>]

Steve Ball wrote:
> Joe English wrote:
> >[...] would it be a good idea to switch to the
> > official expat release hosted at SourceForge?
>
> Yes.  My plan was to merge the Ajuba changes into the SF version.

I think this has already been done -- sort of.

As far as I can tell, most of the Scriptics/Ajuba changes
had to do with DTD Infoset items (<!ELEMENT..> and <!ATTLIST...>
declarations), which expat 1.1 did not support.  However,
expat 1.95 (the current version on expat.sourceforge.net)
*does* support these, just in a slightly different way than
what Eric Melski implemented in the tclexpat version of expat.

[ Eric -- can you confirm or deny this? ]


> > Unfortunately the two versions are not _entirely_ compatible,
> > but the required changes (to dom::c anyway) look fairly minor.
>
> dom::c shouldn't even know about (tcl)expat; it should be using the
> new C API in TclXML v2.0.  TclXML itself then handles the interface
> to the parser class implementation.

True.  But in the meantime, dom::c is still fairly tightly coupled to
the expat parser so I was wondering about near-term changes.


--Joe English

  jen...@fl...

Re: [Tclxml-devel] Switch to SourceForge version of expat?

[Eric M. <er...@in...>]

On Mon, 11 Dec 2000, Joe English wrote:

> Steve Ball wrote:
> > Joe English wrote:
> > >[...] would it be a good idea to switch to the
> > > official expat release hosted at SourceForge?
> >
> > Yes.  My plan was to merge the Ajuba changes into the SF version.
> 
> I think this has already been done -- sort of.
> 
> As far as I can tell, most of the Scriptics/Ajuba changes
> had to do with DTD Infoset items (<!ELEMENT..> and <!ATTLIST...>
> declarations), which expat 1.1 did not support.  However,
> expat 1.95 (the current version on expat.sourceforge.net)
> *does* support these, just in a slightly different way than
> what Eric Melski implemented in the tclexpat version of expat.
> 
> [ Eric -- can you confirm or deny this? ]

I can confirm that the changes I made were to allow us to extract element
and attribute list declarations, yes.  And it looks like expat 1.95 does
support these as well.

   Eric Melski                            The Other Tcl Guy
   ericm at interwoven.com                Interwoven, Inc.