Re: Xerces internal use of .c include files

2005-02-20 Thread David Cargill
Please respond to include files x

Re: Xerces internal use of .c include files

2005-02-18 Thread James Berry
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

Re: Xerces internal use of .c include files

2005-02-18 Thread david_n_bertoni
> - 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

Re: Xerces internal use of .c include files

2005-02-18 Thread James Berry
--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

RE: Xerces internal use of .c include files

2005-02-18 Thread Dean Roddey
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

Re: Xerces internal use of .c include files

2005-02-18 Thread James Berry
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

Xerces internal use of .c include files

2005-02-18 Thread James Berry
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. Since this is also, confusingly, the extension typically used for straight-c files, I'd like to propose that we change this. I think we have two choices:

include files

2001-10-24 Thread muteki muteki
Hi, I have downloaded both xerces-c1_5_1-linux.tar.gz and xerces-c-src1_5_1.tar.gz. When I did a diff for the two include directories, I found them somewhat different. (Not only the platform specific stuff but something inside the idom directory.) Is this something expected? Thanks, --Chris

Re: [Why were <> used instead of "" for include files?]

2001-06-05 Thread kiuma
"Mitchell, Raymond" <[EMAIL PROTECTED]> wrote: > I was just wondering why the include directives in Xerces-C use the <> > system path indicators instead of the "" user path indicators. > > Thanks, > Ray > > - > To unsubscribe, e

Re: Why were <> used instead of "" for include files?

2001-06-04 Thread Dean Roddey
Monday, June 04, 2001 5:28 PM Subject: Why were <> used instead of "" for include files? > I was just wondering why the include directives in Xerces-C use the <> > system path indicators instead of the "" user path indicators. > > Thanks, > Ray >

Why were <> used instead of "" for include files?

2001-06-04 Thread Mitchell, Raymond
I was just wondering why the include directives in Xerces-C use the <> system path indicators instead of the "" user path indicators. Thanks, Ray - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAI