Hi, I would like to be pushy about some annoying issues that have gotten notably worse since v2.1 regarding the coding styles, conventions, and practices, used in Xerces-C development.
I would like to request that developers of Xerces-C cease using ALL_CAPS_NAMES for anything other than for preprocessor macros. Shortly after 2.1 was released I complained about issues regarding conflicts between your enums and preprocessor macros defined in other third-party libraries. Then it just occurred in a few isolated places in Xerces-C. Please, use ALL_CAPS_NAMES only for macros - that is after all a basic convention that most people have followed for the past two decades. A second practice I would like to suggest is that any time code is submitted into source control, someone actually tried it out with warnings cranked all the way up. Don't submit with warnings. I am literally seeing thousands of lines of warnings emanating from Xerces-C 2.6 - far worse than in 2.1. A third practice that I find frustrating is the use of ".c" file extensions for C++ code. Perhaps on case-sensitive file systems which distinguish ".C" from ".c" it works, but on Windows it does cause some issues - especially for code generating automated build systems. Thank you, -------------------------------------------------- Robert Buck The MathWorks [EMAIL PROTECTED] 3 Apple Hill Dr www.mathworks.com Natick, MA 01760 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
