Re: [xml] Bug in 2.4.3 in xmlEncodeEntitiesReentrant

[Daniel Veillard <veillard redhat com>]

On Sat, Sep 08, 2001 at 04:25:13AM +0800, Steve Underwood wrote:
> For XML (with its anything that isn't exiactly right is 100% wrong
> policy) I think it is clear the routine should simply exit, although it
> is not obvious how it should return an error status back to the caller
> (return a NULL pointer, maybe). For HTML things are, as usual, greyer.

  Well XML defines the rules strictly for parsing, but not really
for saving a modified tree.

> *** Nasty bodge alert ***
> To get around my current problem I am simply incrementing the current
> character pointer before the continue statement. This stops the lockup,
> and since the data stream was bad the result is really no worse. The is
> most certainly not the right thing, though.

  Sounds a good enough solution until better is provided,

Daniel

-- 
Daniel Veillard      | Red Hat Network http://redhat.com/products/network/
veillard redhat com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/