Yes, it is alive.
Fred Smith
Senior Applications Programmer/Analyst
Computrition, Inc.
175 Middlesex Turnpike
Bedford, MA 01730
ph: 781-275-4488 x5013
fax: 781-357-4100
From: xml [mailto:xml-boun...@gnome.org] On Behalf Of Alexey Neyman
Sent: Sunday, April 21, 2013 12:23 AM
To: xml@gnome.org
Fixes compiler warning
From fabdca3c0314e4ede352dbab8fb50017d78fda52 Mon Sep 17 00:00:00 2001
From: Nikolay Sivov nsi...@codeweavers.com
Date: Tue, 30 Apr 2013 17:45:36 +0400
Subject: [PATCH] Cast encoding name to char pointer to match arg type
---
parser.c |2 +-
1 file changed, 1
Nothing wrong with it -- if they plan to incorporate your changes into
the system. I made a layer of abstraction because there were things I
wanted different that they would not incorporate, because I wanted
functions that did multiple libxml2 functions instead of coding
everything by hand
It is hard to argue with someone that is technically correct. I am
glad they mandated order as I have always programmed that way. Now I
can sleep better, thanks :-)
However, I am old, experienced, etc. C was not what it is now 30 years
ago. libxml came along and solved a problem. It is
I agree, Daniel -- I love them -- and have done VERY well with them.
Rock solid code and for me, easy to understand and use. I've thanked
you before I'll thank you again. E
On 5/3/2013 7:23 AM, Daniel Veillard wrote:
On Thu, May 02, 2013 at 08:39:47AM +0400, Nikita Churaev wrote:
Daniel said The key point is the absolute imperative of keeping API and
ABI
stability.
I would add -- ALL changes must be 100% compatible -- with ALL of the O/S libxml2 runs
on. Which is daunting. The switch from libxml to libxml2 was a minimal change despite a
vast increase in functions
I agree with everything except ... I still use plain old C ... I just
make my wrappers manage a lot of the underlying things. I would
moderate your description a little -- these are low-level routines. It
would be like comparing C to C++ -- it is not that C is so limited, it
is for a
Dear creators of libxml2,
I think I found a slight mistake in function xpath.c:xmlXPathStringEvalNumber()
of libxml2 version 2.9.0.
For data type float in xml files resp. xml schemas
[1] states The mantissa must be a decimal number.
[2] contains details:
An optional leading sign is
I never thought of it ... I just code as suggested:
node-parent == node-doc or node-parent-type ==
XML_ELEMENT_NODE/XML_DOCUMENT_NODE and so on before you assume it really
is a xmlNode
In fact, I always test the type before doing anything EXCEPT that one node-parent
== node-doc test which
I think I am missing something ... I don't think it really merges ...
it is comparing the address of the node elements, e.g.
if ((parent-last != NULL) (parent-last-type == XML_TEXT_NODE)
(parent-last-name == cur-name)
(parent-last != cur)) {
/* this merge simply
On Mon, May 06, 2013 at 12:41:22PM +, Kuhnke, Christoph (I/EF-56, extern)
wrote:
Dear creators of libxml2,
Hallo,
might be better to subscribe to the list so i don't have to dig your
messages in the mailing-list bounces, which I tend to forget doing !
I think I found a slight mistake
11 matches
Mail list logo
