Hi James,
Not that I am arguing against but the templates use the define
XERCES_TMPLSINC (ie. #if !defined(XERCES_TMPLSINC)) to determine whether
or not to include the .c files. Inside src/xercesc/Makefile.incl for HPUX
if the compiler is not aCC then this define is set. I am not sure what
compi
On Feb 18, 2005, at 3:51 PM, [EMAIL PROTECTED] wrote:
- Convert these files into actual templates, perhaps. I haven't
looked enough into the implementations to know whether this is
possible, or to discover what else might prevent us from doing this. I
do know that we use templates elsewhere in
> - Convert these files into actual templates, perhaps. I haven't
> looked enough into the implementations to know whether this is
> possible, or to discover what else might prevent us from doing this. I
> do know that we use templates elsewhere in Xerces, so this shouldn't
> break any com
--Original Message-
From: James Berry [mailto:[EMAIL PROTECTED]
Sent: Friday, February 18, 2005 3:39 PM
To: xerces-c-dev@xml.apache.org
Subject: Re: Xerces internal use of .c include files
On Feb 18, 2005, at 3:32 PM, James Berry wrote:
In thinking about changes for 3.0, another item I came up with
n/CTO, Charmed Quark Systems
[EMAIL PROTECTED]
www.charmedquark.com
-Original Message-
From: James Berry [mailto:[EMAIL PROTECTED]
Sent: Friday, February 18, 2005 3:39 PM
To: xerces-c-dev@xml.apache.org
Subject: Re: Xerces internal use of .c include files
On Feb 18, 2005, at 3:32 PM, James
On Feb 18, 2005, at 3:32 PM, James Berry wrote:
In thinking about changes for 3.0, another item I came up with is the
use of the .c extension for C++ files included as pseudo-templates.
Actually, I think I mischaracterized the use of these files. In most
cases they are used to for the implementat
