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...?
So this option doesn't really apply.
- Change the extensions on the files to something else. Suggestions are welcome. .tcc comes to mind, though I know gcc uses this for some of it's code and I don't want to confuse it. Does anybody know of any standard usage?
I'd recommend we do at least the later, and maybe the former if somebody has the time to do it.
Comments?
-jdb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
