jasons 2002/12/09 11:39:49
Modified: perl README
Log:
* README (Repository):
updated the build requirements
Revision Changes Path
1.21 +15 -42 xml-xerces/perl/README
Index: README
===================================================================
RCS file: /home/cvs/xml-xerces/perl/README,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- README 7 May 2002 06:06:56 -0000 1.20
+++ README 9 Dec 2002 19:39:49 -0000 1.21
@@ -11,7 +11,7 @@
-1) Current Release: XML::Xerces 1.7.0-1
+1) Current Release: XML::Xerces 2.0.0-0
========================
XML::Xerces is the Perl API to the Apache project's Xerces XML parser. It
@@ -80,21 +80,23 @@
installed it will work fine.
If you plan on using Unicode, I *strongly* recommend upgrading to
- Perl-5.7.2, the latest development version. There have been significant
+ Perl-5.8.0, the latest stable version. There have been significant
improvements to Perl's Unicode support.
3.3) The Apache Xerces C++ XML Parser
------------------------
#### NOTE: ####
- Required version: 1.7.0
+ Required version: 2.0.0
###############
- (which can be downloaded from the apache archive <URL:
- http://xml.apache.org/dist/xerces-c/stable/> ) You'll need both the
- library and header files, and to set up any environment variables that
- will direct the XML::Xerces build to the directories where these
- reside.
+ Which can be downloaded from the apache archive:
+
+ http://xml.apache.org/dist/xerces-c/stable/
+
+ You'll need both the library and header files, and to set up any
+ environment variables that will direct the XML::Xerces build to
+ the directories where these reside.
4) Development Tools
========================
@@ -119,8 +121,7 @@
do not work for your perl distribution. The pre-generated files have
been created by SWIG 1.3 and work under perl-5.005 and perl-5.6.
- This port will only work with SWIG 1.3.12 (which is currently only
- available via CVS).
+ This port will only work with SWIG 1.3.15+.
If your planning to use SWIG, you can set the environment variable SWIG
to the full path to the SWIG executable before running perl
@@ -153,8 +154,8 @@
Unpack the archive in a directory of your choice. Example (for UNIX):
- * tar zxvf XML-Xerces-1.7.0-1.tar.gz
- * cd XML-Xerces-1.7.0-1
+ * tar zxvf XML-Xerces-2.0.0-0.tar.gz
+ * cd XML-Xerces-2.0.0-0
5.4) Examine Makefile.PL
------------------------
@@ -188,7 +189,7 @@
6) Build XML::Xerces
========================
- A) Go to the XML-Xerces-1.7.0-1 directory.
+ A) Go to the XML-Xerces-2.0.0-0 directory.
B) Build XML::Xerces as you would any perl package that you might get from
CPAN:
* perl Makefile.PL
@@ -222,7 +223,6 @@
* DOM Serialization API
* Implementing Perl handlers for C++ event callbacks
* handling C++ exceptions
- * DOM vs. IDOM: Incompatible Change
8.1) String I/O
------------------------
@@ -312,33 +312,6 @@
die(), but if more is needed, see the files t/XMLException.t,
t/SAXException.t, and t/DOMException.t for details on how to roll your
own handler.
-
- 8.7) DOM vs. IDOM
- ------------------------
-
- *Incompatible Change*
-
- Since Xerces-C-1.5 there has been an experimental DOM implementation
- (IDOM) that is much more efficient than the old DOM implementation. As
- of XML::Xerces-1.7.0_0 all DOM methods have been switched to the IDOM
- implementation, and the old DOM implementation is no longer available.
-
- This has made the codebase much smaller and more efficient, but there
- are some important issues to watch out for, and some code written to
- use the old DOM implementation may not work:
-
- * DOM_Node::isNull(): is no longer available. In the old DOM API, you could
- receive a valid DOM_Node that was really just a wrapper for a NULL
- pointer, so before you did anything, you always had to check it
- using the isNull() method. Using the new DOM, you will get undef
- instead of an object, so you would instead check using defined().
- * DOMParser::setToCreateXMLDeclTypeNode(): the now DOM API follows the W3C
- specification more closely than the old one did, so this method is
- no longer available.
- * DOM_Document::createDocument(): the new DOM API follows the W3C
- specification more closely than the old one did, so this method is
- no longer available, use DOM_DOMImplementation::createDocument()
- instead.
9) Sample Code
========================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
