[ http://issues.apache.org/jira/browse/XERCESC-1489?page=comments#action_12320908 ]
James Berry commented on XERCESC-1489: -------------------------------------- The problem is that in some places we use an unsigned int to represent "scope", and in others we use an "int". So we're damned if we do and damned if we don't. I know that there were literally hundreds of warnings from the 2.6 code; are there less now? In which case we should track down and change any of the definitions that define scope as an "int", like fEnclosingScope in SchemeElementDecl.hpp. > Annoying compiler warnings > -------------------------- > > Key: XERCESC-1489 > URL: http://issues.apache.org/jira/browse/XERCESC-1489 > Project: Xerces-C++ > Type: Bug > Components: Validating Parser (Schema) (Xerces 1.5 or up only) > Versions: 2.7.0 > Environment: RedHat Linux 7.3, g++ v3.3.3 > Reporter: David Ergo > Priority: Minor > > When compiling a program with #include <xercesc/sax2/XMLReaderFactory.hpp>, > like SAX2Count, with warnings enabled (-Wall instead of -w), we get the > following compiler warning : > /usr/local/xerces-c/include/xercesc/validators/schema/SchemaElementDecl.hpp: > In > member function `virtual bool > xercesc_2_7::SchemaElementDecl::isGlobalDecl() > const': > /usr/local/xerces-c/include/xercesc/validators/schema/SchemaElementDecl.hpp:508: > warning: comparison > between signed and unsigned integer expressions -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
