Hi Martin, I agree with you regarding the inconsistency between TraverseSchema::isOccurenceRangeOK(int,int,int,int) and ContentSpecNode::setMaxOccurs(unsigned int). We have fixed that. The min/maxOccurs are now passed/stored as int values.
Regards, Khaled Martin Kalen wrote: > In TraverseSchema.cpp, line 5426 in the v1.7.0 release, there is an > assignment of > SchemaSymbols::UNBOUNDED (defined in SchemaSymbols.hpp to be -1) > to the unsigned integer maxOccurs, used in a call to > ContentSpecNode::setMaxOccurs(unsigned int). > > Of course this gives a compiler warning (with several different > compilers) about passing a negative value as unsigned int. Even the > comment about the private field fMaxOccurs in ContentSpecNode.hpp says > that -1 is the unbounded value, yet the field is declared as "unsigned > int". > > There seems to be an inconsistency between e.g. > TraverseSchema::isOccurenceRangeOK(int,int,int,int) and > ContentSpecNode::setMaxOccurs(unsigned int). > > Any thoughts on this? > > Martin > > --------------------------------------------------------------------- > 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]
