Re: [xml] xmlKeepBlanksDefault() behavior



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Samedi 17 Mai 2003 18:46, vous avez écrit :
From: Daniel Veillard [mailto:veillard redhat com]
  What is the problem in practice. Why would changing this
"improve" the
library ? I need a rationale based on a concrete case before deciding
to change something at that level, people may have built expectation
on the existing behaviour and I really need to be convinced before
changing something so core to libxml2 and libxslt processing.

I think he's saying that
1. It's a good idea to save this global setting before setting it, so it
can be restored later, so that code that uses libxml doesn't interfere with
other code that also uses libxml.
2. That doesn't work now.


Indeed. Althougt I went a bit fast to a radical conclusion, I mainly wanted to 
know wether this behavior should be considered as 'normal'.

It's a problem that we are having with libxml++.

Even if the current behavior is changed, we'll have to make a small workaround 
for older versions.

Regards,

Christophe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+yeHuB+sU3TyOQjARAqc7AJ90t3bhxDz97/cC+jnzyxYmEE9g7ACgrra9
leehT92ml61ftSdeUH4beDs=
=FP69
-----END PGP SIGNATURE-----




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]