(specifically, make sure args are not NULL).
If the expected value is not the right length, include the value found in
the error message, to make problems easier to diagnose.
_xml_failure(): Clean up the output message so the first line doesn't
wrap in the typical case.
CharData typedef: If count is less than 0, consider it "unset". This
is used in the new support to check attribute values.
accumulate_characters(): Handle storage->count < 0. Allow XML_Char
to be more than one byte.
accumulate_attribute(): New function: store the value of the first
attribute encountered in parsing. This needs the concept of a
CharData that is unset to allow capturing a value that is an empty
string.
check_characters(): Handle storage->count < 0. Allow XML_Char to be
more than one byte.
run_character_check(): Create a local parser so that both
run_character_check() and run_attribute_check() can be used in a
single test function.
run_attribute_check(): New function: check that the value of the
first attribute in a document matches the expected value.
This modifies the patch for style (slightly).
The style of these files is also slightly modified in an attempt to create
more consistency. (But that mostly swamps the feature patch.)
data; let Expat determine the proper encoding from the XML source text.
Added several tests relating to supposed mis-interpretation of Latin-1;
these show that Expat (at least in the CVS version) is properly decoding
the Latin-1 text and generating the proper UTF-8 output.
This closes SF bug #491986, #514281.
* use libtool to compile/link all programs
* remove */Makefile.in and remove them from configure
* remove autom4te.cache after running autoconf
* remove .o from the FILEMAP logic in configure and the Make system;
provides more flexibility in the Makefile to use it
* for VPATH builds: create the build subdirs by running
"make mkdir-init" from the configure script
* adjust .cvsignore files to account for presence of .libs now
attributes is properly collapsed according to Section 3.3.3 of the spec.
This is the first even slightly complicated test; boy are these painful in
C! Had to add a test of a helper routine as well; that just uses assertions
since the test framework should not be dealing with tests of the tester,
just of Expat.
Added a helper to make the failure messages more useful when Expat produces
an unexpected error code; we now include the error message and location from
Expat. This is mostly useful when developing a new test.