Re: [xml] Important: possible incompatible changes ahead for 2.9.0 !



On Fri, Aug 10, 2012 at 09:32:13AM +0200, Johan Corveleyn wrote:
On Mon, Aug 6, 2012 at 10:17 PM, Johan Corveleyn <jcorvel gmail com> wrote:
[...]
See also this report in the Debian tracker:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445961

From what I understood of the issue comments, there was some
discussion back and forth (also about the lack of
mailinglist-discussion, but that's beside the point now), including
some talk about ABI incompatibility.

If this issue isn't addressed already, maybe this is an opportunity to
take this along?

This issue affects us mainly because when we're schema-validating some
big XML files with xmllint (files with around 130,000 lines -- and no,
those are not automatically generated :-), but accumulated
configuration (over 10 years) of a very big application). Validation
errors after line 65535 always get reported as line 65535, making it
sometimes hard to find the problem (if you've made multiple edits).

Thanks for all your efforts.

Can someone answer the above question(s) please? Would be interesting
to know ...

  I don't want to extend the size of a node by default. That's something
I said and I don't plan to revisit that decision. Also 2.9.0 is not
a magical release where I would break ABI compatibility (I don't expect
to do that in the foreseable future !)

 That said there are ways to get "long" line numbers stored in adjacent
nodes c.f. xmlGetLineNo()
  But not knowing how you actually use the parser nor how you
use the schemas validation, I cant tell if you can extract full line
numbers. It should be possible in the xmlReader for example.
But I don't know how you validate, maybe this could be added, but
I have no details from you to reproduce your specific situation so ...

Daniel


-- 
Daniel Veillard      | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
daniel veillard com  | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library  http://libvirt.org/



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