You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Robert Buck (JIRA)" <xe...@xml.apache.org> on 2005/01/19 22:27:18 UTC
[jira] Created: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Change all enum values from ALLCAPS to MixedCase
------------------------------------------------
Key: XERCESC-1327
URL: http://issues.apache.org/jira/browse/XERCESC-1327
Project: Xerces-C++
Type: Bug
Components: Build
Versions: 2.6.0
Environment: All
Reporter: Robert Buck
The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Stefan Letz (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57883 ]
Stefan Letz commented on XERCESC-1327:
--------------------------------------
I really don't like the idea of having some parts of the Xerces lib using camel case for enums while other parts keep using all caps. To me, this is simply inconsistent.
By the way: "Parsers don't kill people. People do.". ;)
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Robert Buck (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57834 ]
Robert Buck commented on XERCESC-1327:
--------------------------------------
That you need release compatibility is fine, I agree with this (though I am puzzled to find that an upgrade from 2.1 to 2.6 did require changes to our code in order to compile at all).
I would like this issue addressed in the next major release. And if developers would, please, stop submitting ALLCAPS identifiers for things other than preprocessor macros, that would be greatly appreciated.
Thanks
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Stefan Letz (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57887 ]
Stefan Letz commented on XERCESC-1327:
--------------------------------------
I'm sorry if you felt offended. I absolutely understand your point of view, as well as I understand your change request.
What I wanted to say: if the case of enums is to be changed, this should be done for the whole API.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Jesse Pelton (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57852 ]
Jesse Pelton commented on XERCESC-1327:
---------------------------------------
Case matters, for (at least) three reasons. First, it's easier for a user to determine that the identifier used by the implementation is intended to match the one in the spec if the case is the same. Second, it's a slippery slope. Why not use camel case and get rid of those wasteful underscores, so INVALID_STATE_ERRS becomes InvalidStateErrs? But most important, the code becomes tied to a specific implementation. If all implementations follow the specification closely, users can much more simply move to a different one if there is reason to.
I agree that INVALID is a horrible identifier. Maybe it should be changed. If it isn't part of a spec (I couldn't find it in one), I'd be all for changing it.
I think we're better off addressing specific cases like this than making blanket changes. Bear in mind that part of the responsibility for the problem lies with developers who 1) continue to use manifest constants when better constructs have long been available and 2) choose broad names like INVALID for such constants. I would expect such problems to decrease over time as developers use more modern language features.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Alberto Massari (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_60970 ]
Alberto Massari commented on XERCESC-1327:
------------------------------------------
Just adding another enum giving troubles: S_NORMAL is defined in the Win32 headers (WinBase.h) and conflicts with RegxParser::S_NORMAL (util\regx\RegxParser.hpp)
Alberto
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Jesse Pelton (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57850 ]
Jesse Pelton commented on XERCESC-1327:
---------------------------------------
It looks to me like some enums are all caps and some are mixed case. Every uppercase enumeration in Xerces 2.5 that I checked was specified in all caps in the DOM specs. (I looked at the node types (ELEMENT_NODE et al), exception codes (DOMSTRING_SIZE_ERR et al), LSParser actions types (ACTION_APPEND_AS_CHILDREN et al), DOMError severity levels ([DOM_]SEVERITY_WARNING et al), DOMImplementationLS modes (MODE_SYNCHRONOUS, MODE_ASYNCHRONOUS), filter actions (FILTER_ACCEPT et al), range comparison types (START_TO_START et al), and range exceptions (BAD_BOUNDARYPOINTS_ERR and INVALID_NODE_TYPE_ERR) before I got tired of looking.)
It seems to me that Xerces must match this casing, since Xerces is an implementation of the spec.
(The Xerces 2.5 TREE_POSITION... identifiers appear to map roughly to DOCUMENT_POSITION... identifiers in the spec. I'm not sure why the names differ. Another bug, perhaps.)
Whether it makes sense to implement these all caps identifiers as macros rather than enumerations in order to match programming convention is another question. I'd vote against it, because you lose the ability to enforce the correct parameter type in function calls, and this seems more important.
Are there any enumerated names that are all caps that are not drawn from the spec? If so, they're candidates for change. Otherwise, I don't think there's much to be done.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "cargilld (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57794 ]
cargilld commented on XERCESC-1327:
-----------------------------------
Robert,
Making this change will break source code compatibility which violates our release policy (http://xml.apache.org/xerces-c/faq-contributing.html#faq-2). When we reversion this is something we can change as we aren't tied to source code compatiblity for a new version but we are for a new release.
David
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Robert Buck (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57851 ]
Robert Buck commented on XERCESC-1327:
--------------------------------------
I completely disagree with you. Xerces-C does not have to match the case.
Just because a language agnostic specification uses ALL_CAPS for enumeration values does not imply that every language implementation must use ALL_CAPS case. This goes for any part of the specification; if something does not naturally, nor by conventional wisdom, nor in general practice, map easily into the target language, you adapt it. Because Java did not support enum's, did that mean that the Apache Group bailed out on writing a Java DOM implementation, or that others should not have done so? No, by no means! You adapt the specification to the specific situation.
In this specific case I am asking the Apache Group to apply the same consideration here, as they have done in other situations where they have deviated from a specification in order to provide a language specific implementation (e.g. Xerces-Java), that when a the specification has an enum value, for instance INVALID, you don't go off and write this as all caps in C++. Dang it, how many third-party libraries define INVALID as an expression that checks an error code range? Many!
For C & C++, conventional wisdom for two decades now has been to leave ALL_CAPS reserved for macros, period. With regards to the enum values in Xerces-C, for developers sake (and their sanity), change them to mixed case.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Robert Buck (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57894 ]
Robert Buck commented on XERCESC-1327:
--------------------------------------
I'm not offended, and I hope I am not offending anyone myself. But I do, and did, want to make it abundantly clear that for some software a silent incorrect result can cause death. And I do feel that perhaps people were not feeling the gravity of the situation, at least for developers of critical software.
I really wish that as standard practice for Xerces-C, that builds would always occur with warning levels set to their highest, and as a matter of practice, any time someone commits a file - they are responsible for ensuring the file is warning free. In this way, a bulk of the code would be cleaned up in little time at all.
I have brought up the issue of warnings once before, and specifically I suggested that Xerces-C should be built warnings free, with warnings cranked all the way up. And as I recall someone said, "that's useless because it's safe to ignore most warnings anyway". Recent situations show how valuable warnings can be at identifying potential bugs, and can spur questions where people ask, "is this really the best way of doing such and such". Sometimes refactoring, or redesign, results. And that's great.
I hope we can come to some agreement on the present issue.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Robert Buck (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57882 ]
Robert Buck commented on XERCESC-1327:
--------------------------------------
[1] The specific case where I "detect" a problem is with the PSVIDefs enums. Since PSVI, last I was aware, is not part of any W3 Spec, I see no reason to not change these to camel case.
[2] The only reason I actually found this was that a third party library defines these specific ALL_CAPS values as ***EXPRESSIONS***. And this is precisely what really concerns me... If the ALL_CAPS preprocessor macro were not an expression, but a scalar value, what would have been the result? Perhaps an incorrect result? Is that possible?
I think it is better to break with a standard to adapt it to a particular programming language, than to kill people. And yes, incorrect results can kill.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase
Posted by "Robert Buck (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57884 ]
Robert Buck commented on XERCESC-1327:
--------------------------------------
> By the way: "Parsers don't kill people. People do.". ;)
Perhaps you are trying to make light of the matter, but I hardly find it funny. This is a serious issue, as are most of the defects I have been finding. Would it be funny if a root cause analysis of the explosion of a prototype JSF fighter, that killed one of our military personel, and cost billions, was traced back to a coding error in Xerces-C, and introduced by yourselves? Yes, you are dead right; people do kill people.
The very reason I hound people on these sorts of things is because, yes, the devil _is_ in the details. Where loss of life is a factor, details become paramount.
> Change all enum values from ALLCAPS to MixedCase
> ------------------------------------------------
>
> Key: XERCESC-1327
> URL: http://issues.apache.org/jira/browse/XERCESC-1327
> Project: Xerces-C++
> Type: Bug
> Components: Build
> Versions: 2.6.0
> Environment: All
> Reporter: Robert Buck
>
> The enum values in Xerces-C are in ALLCAPS, which violates general programming practice, which reserves ALLCAPS identifiers for C preprocessor macros. This is a huge problem for people integrating diverse 3rd-party libraries and Xerces-C, as the enum values often collide with macro expressions. The result is thousands of lines of nearly indecipherable errors being emitted from compilers.
> Please change all enum values to "MixedCase". If you happen to be aware of any other ALLCAPS identifiers in Xerces-C, change those too.
> This is very critical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org