The only reason that was done was that, back in the stone age, I think that some of the compilers we supported would only support templates in this form (CFront based ones or something, I can't remember?) So we could support those plus newer ones by just including the .c file into the .h/hpp file for more modern compilers. So we were able to kill both birds with one stone.
I would hope that such compilers are now pushing up daisies, and it would be fine to just pull the .c files into the .h/hpp files and be done with it. ------------------------------------- Dean Roddey Chairman/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 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 implementation portion of real, actual, 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: > - 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 compiler compatibility...? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
