One possible way to find out if -DHAS_BOOL should be used, is to query the
perl -V for the Compiler info. I'm sure there is another way of doing this,
but I can't think of any with MakeMaker, only through C preprocessor. I can
try to compile without -DHAS_BOOL, since now after looking at perl -V it was
not compiled with that option, so not sure why I needed it for Xerces, but
I'll look at it tonight and try to recompile 1.3 without it.
Definitelly Perl needs Xerces right now, probably more than any other XML
module, due to it's schema support progress, and having compatibility with
most platforms is very important. Windows is really important in my
opinion, though I never run production apps on windows, it's a good platform
(and a standard one, if you work for a large corporation) to do development
before rolling to a *NIX server. I've had 137 downloads for the last 13
days. But 1.3 does not have schema support, so I can imagine that this will
be very highly used on windows, since it's the only perl module that has
such schema support.
Ilya
-----Original Message-----
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Sterin, Ilya
Sent: 07/18/2001 11:49 AM
Subject: Re: XML::Xerces port to windows
"Jason E. Stewart" <[EMAIL PROTECTED]> writes:
> This is really excellent news! I'm glad that we can say there is
> something available for windows. I'd really appreciate knowing what
> you needed to change in Makefile.PL to make it work for you (there was
> no attachment in your previous message).
Sorry, your file was attached, I just wasn't paying attention. You
made very few changes.
I can make the file simpler by removing the need for find:
1) Hardcoding the names of the Handler/*.o files in Makefile.PL
2) Moving the need for find into the XERCES_DEVEL if statement. That
way normal users have no need for it.
Xerces-C 1.5.1 is going to be released in a couple of days, and will
include a major memory-lead patch, I'll release Xerces.pm-1.5.4 after
that and I'll inlcude these Makefile changes.
I need a way to automatically detect whether compilers require the
HAS_BOOL flag. Some require it, some don't care and some fail if it's
included. Any suggestions?
I wonder how Xerces-C does it...
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
