You are viewing a plain text version of this content. The canonical link for it is here.
Posted to p-dev@xerces.apache.org by "Harmon S. Nine" <hn...@netarx.com> on 2001/02/24 03:33:26 UTC
xerces-perl module for linux (here it is)
Hi folks. Attached is a (62k) b-zipped tarball that should be a complete
xerces-perl build and install. This is what we're using at Netarx.
The tarball behaves like a standard perl extension that you might
download from CPAN.
I.e. once it is untarred, in the resulting directory type:
perl Makefile.PL
make
make test
make install
Currently, the only platform on which this has been tested is debian-linux.
It probably will need some mods to work on other platforms.
NICE NEW THINGS ABOUT THIS VERSION OF XERCES-PERL:
----------------------------------------------------
Good-bye DOMStrings and transcode calls (hopefully, this is a good
thing, let me know
if it's not). All functions that take DOMString as an argument can now
use either a
DOMString or straight run-of-the-mill perl-string. Functions that
originally returned a DOMString now return straight perl-strings. Thus,
calls like
$element = $document->createElement( new DOMString('foo') );
$value = $element->getNodeValue->transcode
are now just
$element = $document->createElement('foo');
$value = $element->getNodeValue
In fact, any and all functions in the xerces-c API that take/return
string-like
values, such as XMLCh *, take/return straight strings from/to perl.
This is all thanks to SWIG typemaps.
One drawback, nothing returns a DOMString (big deal).
AS WELL, all standard InputSources that come with the xerces-c
distribution, i.e.
LocalFileInputSource, StdInInputSource, MemBufInputSource, and
URLInputSource
now all work from xerces-perl. Those previously introduced,
MemoryInputSource
and FileInputSource, still work.
Note: the MemBufInputSource in the xerces-c API takes four arguments:
the memory buffer
the length of the buffer
a pseude-system-id for the buffer
an "adoptbuffer" flag.
In perl, MemBufInputSource takes only two of these arguments:
the memory buffer (i.e. a perl-string containing the XML document)
the pseudo-system-id for the buffer.
The length argument is determined automatically, and the adoptbuffer is
always set to
true. This is again thanks to SWIG typemaps.
Cheers.
-- Dr. Harmon S. Nine
Netarx, Inc.
Re: xerces-perl module for linux (here it is)
Posted by Steve Litt <sl...@troubleshooters.com>.
Everyone on the list --
I'm sorry I sent this to the list. I was rushing and didn't realize that
xerces-p-dev@xml.apache.org was a mailing list (yes, I was rushing that
much). I meant to send it only to Harmon.
Steve
Steve Litt
Webmaster, Troubleshooters.Com
http://www.troubleshooters.com
slitt@troubleshooters.com
At 06:54 PM 2/28/01 -0500, you wrote:
>Hi Harmon,
>
>I'd like very much to include word of Xerces for Perl in the upcoming March
>Troubleshooting Professional Magazine, but to do that I need to steer my
>readers to some place where they can read more about the progress of
>Xerces-Perl, and maybe alpha-test downloads. I'm going to press tomorrow
nite.
>
>The March TPM will be read by somewhere between 1000 and 20,000 people
>during the month of March, depending on the level of incoming links.
>Traditionally, tutorial type TPM issues get about 6,000 visits during their
>first month.
>
>So if you can provide me with such a URL, please do so quickly.
>
>Thanks Harmon, and congratulations on Xerces-Perl.
>
>Steve
>
>Steve Litt
>Webmaster, Troubleshooters.Com
>http://www.troubleshooters.com
>slitt@troubleshooters.com
>
>
>
>At 09:33 PM 2/23/01 -0500, you wrote:
>>Hi folks. Attached is a (62k) b-zipped tarball that should be a complete
>>xerces-perl build and install. This is what we're using at Netarx.
>>The tarball behaves like a standard perl extension that you might
>>download from CPAN.
>>I.e. once it is untarred, in the resulting directory type:
>>
>>perl Makefile.PL
>>make
>>make test
>>make install
>>
>>Currently, the only platform on which this has been tested is debian-linux.
>>It probably will need some mods to work on other platforms.
>>
>>
>>
>>NICE NEW THINGS ABOUT THIS VERSION OF XERCES-PERL:
>>----------------------------------------------------
>>Good-bye DOMStrings and transcode calls (hopefully, this is a good
>>thing, let me know
>>if it's not). All functions that take DOMString as an argument can now
>>use either a
>>DOMString or straight run-of-the-mill perl-string. Functions that
>>originally returned a DOMString now return straight perl-strings. Thus,
>>calls like
>>
>>$element = $document->createElement( new DOMString('foo') );
>>$value = $element->getNodeValue->transcode
>>
>>are now just
>>
>>$element = $document->createElement('foo');
>>$value = $element->getNodeValue
>>
>>In fact, any and all functions in the xerces-c API that take/return
>>string-like
>>values, such as XMLCh *, take/return straight strings from/to perl.
>>
>>This is all thanks to SWIG typemaps.
>>One drawback, nothing returns a DOMString (big deal).
>>
>>AS WELL, all standard InputSources that come with the xerces-c
>>distribution, i.e.
>>LocalFileInputSource, StdInInputSource, MemBufInputSource, and
>>URLInputSource
>>now all work from xerces-perl. Those previously introduced,
>>MemoryInputSource
>>and FileInputSource, still work.
>>
>>Note: the MemBufInputSource in the xerces-c API takes four arguments:
>>the memory buffer
>>the length of the buffer
>>a pseude-system-id for the buffer
>>an "adoptbuffer" flag.
>>
>>In perl, MemBufInputSource takes only two of these arguments:
>>the memory buffer (i.e. a perl-string containing the XML document)
>>the pseudo-system-id for the buffer.
>>
>>The length argument is determined automatically, and the adoptbuffer is
>>always set to
>>true. This is again thanks to SWIG typemaps.
>>
>>Cheers.
>>-- Dr. Harmon S. Nine
>>Netarx, Inc.
>>
>>
>>Attachment Converted: "e:\eudora\attach\xerces-perl-1.3.0.tar.bz2"
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-p-dev-help@xml.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-p-dev-help@xml.apache.org
>
>
xerces-perl module for linux (here it is)
Posted by Steve Litt <sl...@troubleshooters.com>.
Hi Harmon,
I'd like very much to include word of Xerces for Perl in the upcoming March
Troubleshooting Professional Magazine, but to do that I need to steer my
readers to some place where they can read more about the progress of
Xerces-Perl, and maybe alpha-test downloads. I'm going to press tomorrow nite.
The March TPM will be read by somewhere between 1000 and 20,000 people
during the month of March, depending on the level of incoming links.
Traditionally, tutorial type TPM issues get about 6,000 visits during their
first month.
So if you can provide me with such a URL, please do so quickly.
Thanks Harmon, and congratulations on Xerces-Perl.
Steve
Steve Litt
Webmaster, Troubleshooters.Com
http://www.troubleshooters.com
slitt@troubleshooters.com
At 09:33 PM 2/23/01 -0500, you wrote:
>Hi folks. Attached is a (62k) b-zipped tarball that should be a complete
>xerces-perl build and install. This is what we're using at Netarx.
>The tarball behaves like a standard perl extension that you might
>download from CPAN.
>I.e. once it is untarred, in the resulting directory type:
>
>perl Makefile.PL
>make
>make test
>make install
>
>Currently, the only platform on which this has been tested is debian-linux.
>It probably will need some mods to work on other platforms.
>
>
>
>NICE NEW THINGS ABOUT THIS VERSION OF XERCES-PERL:
>----------------------------------------------------
>Good-bye DOMStrings and transcode calls (hopefully, this is a good
>thing, let me know
>if it's not). All functions that take DOMString as an argument can now
>use either a
>DOMString or straight run-of-the-mill perl-string. Functions that
>originally returned a DOMString now return straight perl-strings. Thus,
>calls like
>
>$element = $document->createElement( new DOMString('foo') );
>$value = $element->getNodeValue->transcode
>
>are now just
>
>$element = $document->createElement('foo');
>$value = $element->getNodeValue
>
>In fact, any and all functions in the xerces-c API that take/return
>string-like
>values, such as XMLCh *, take/return straight strings from/to perl.
>
>This is all thanks to SWIG typemaps.
>One drawback, nothing returns a DOMString (big deal).
>
>AS WELL, all standard InputSources that come with the xerces-c
>distribution, i.e.
>LocalFileInputSource, StdInInputSource, MemBufInputSource, and
>URLInputSource
>now all work from xerces-perl. Those previously introduced,
>MemoryInputSource
>and FileInputSource, still work.
>
>Note: the MemBufInputSource in the xerces-c API takes four arguments:
>the memory buffer
>the length of the buffer
>a pseude-system-id for the buffer
>an "adoptbuffer" flag.
>
>In perl, MemBufInputSource takes only two of these arguments:
>the memory buffer (i.e. a perl-string containing the XML document)
>the pseudo-system-id for the buffer.
>
>The length argument is determined automatically, and the adoptbuffer is
>always set to
>true. This is again thanks to SWIG typemaps.
>
>Cheers.
>-- Dr. Harmon S. Nine
>Netarx, Inc.
>
>
>Attachment Converted: "e:\eudora\attach\xerces-perl-1.3.0.tar.bz2"
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-p-dev-help@xml.apache.org