[serialization] warnings in debug build

building vs trunk I got (only in my debug build): boost/archive/basic_binary_oarchive.hpp:89: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oarchive.hpp:95: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oprimitive.hpp:163: warning: comparison between signed and unsigned integer expressions boost/archive/basic_binary_iprimitive.hpp:154: warning: comparison between signed and unsigned integer expressions Best regards Christoph

With what compiler? on whick branch? when? (before or after upload of fixes to address warnings) Robert Ramey Christoph Duelli wrote:
building vs trunk I got (only in my debug build):
boost/archive/basic_binary_oarchive.hpp:89: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oarchive.hpp:95: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oprimitive.hpp:163: warning: comparison between signed and unsigned integer expressions boost/archive/basic_binary_iprimitive.hpp:154: warning: comparison between signed and unsigned integer expressions
Best regards Christoph
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Robert Ramey wrote:
With what compiler? on whick branch? when? (before or after upload of fixes to address warnings) With gcc 4.2.1; with 'trunk' I meant: http://svn.boost.org/svn/boost/trunk I did a svn update this morning, so I guess after the upload of those fixes.
Best regards

and another question Which file was being compiled? Turns out that the emission of warnings (and errors) in code occurs when templates are instantiated. So it's not enough to know where the warning is emitted. Currently, almost all the warning which occur when building the tests have been addressed. Pending are warnings which are emitted when the library is built. Also, I've set the warning level in accordance the new guidlines. In order to address this, it would be helpful to know what level of warning you are using and how it compares with the new guidline Robert Ramey Christoph Duelli wrote:
building vs trunk I got (only in my debug build):
boost/archive/basic_binary_oarchive.hpp:89: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oarchive.hpp:95: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oprimitive.hpp:163: warning: comparison between signed and unsigned integer expressions boost/archive/basic_binary_iprimitive.hpp:154: warning: comparison between signed and unsigned integer expressions
Best regards Christoph
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Robert Ramey wrote:
and another question
Which file was being compiled? one of mine; the warnings listed below are all from assert() statements and I do not think they really depend on my code or the instantiations.
relevant compile flags (I am using): -Wall -W and of course (debug builds) *no* -DNDEBUG
Also, I've set the warning level in accordance the new guidlines. In order to address this, it would be helpful to know what level of warning you are using and how it compares with the new guidline I have not studied the guideline yet.
Best regards Christoph
Christoph Duelli wrote:
building vs trunk I got (only in my debug build):
boost/archive/basic_binary_oarchive.hpp:89: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oarchive.hpp:95: warning: comparison is always true due to limited range of data type boost/archive/basic_binary_oprimitive.hpp:163: warning: comparison between signed and unsigned integer expressions boost/archive/basic_binary_iprimitive.hpp:154: warning: comparison between signed and unsigned integer expressions

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Christoph Duelli Sent: Monday, November 16, 2009 6:41 PM To: boost@lists.boost.org Subject: Re: [boost] [serialization] warnings in debug build
Robert Ramey wrote:
and another question
Which file was being compiled? one of mine; the warnings listed below are all from assert() statements and I do not think they really depend on my code or the instantiations.
relevant compile flags (I am using): -Wall -W and of course (debug builds) *no* -DNDEBUG
Also, I've set the warning level in accordance the new guidlines. In order to address this, it would be helpful to know what level of warning you are using and how it compares with the new guidline I have not studied the guideline yet.
https://svn.boost.org/trac/boost/wiki/Guidelines/MaintenanceGuidelines but very much for discussion and feedback.
and of course (debug builds) *no* -DNDEBUG need adding.
Paul --- Paul A. Bristow Prizet Farmhouse Kendal, UK LA8 8AB +44 1539 561830, mobile +44 7714330204 pbristow@hetp.u-net.com

Paul A. Bristow wrote:
Also, I've set the warning level in accordance the new guidlines. In order to address this, it would be helpful to know what level of warning you are using and how it compares with the new guidline I have not studied the guideline yet.
https://svn.boost.org/trac/boost/wiki/Guidelines/MaintenanceGuidelines Ok, I had a look at the page.
but very much for discussion and feedback. Sorry, I have the feeling this sentence is not quite complete. But then, as I am not a native speaker, maybe I just didn't get it.
Best regards Christoph

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Christoph Duelli Sent: Monday, November 16, 2009 8:42 PM To: boost@lists.boost.org Subject: Re: [boost] [serialization] warnings in debug build
https://svn.boost.org/trac/boost/wiki/Guidelines/MaintenanceGuidelines Ok, I had a look at the page.
but very much for discussion and feedback. Sorry, I have the feeling this sentence is not quite complete. But then, as I am not a native speaker, maybe I just didn't get it.
Well personally *I* have no problem with English - but then I *am* English ;-) But I obviously wasn't clear, I'm sorry I made it difficult for all those doing amazingly well with another language - and I need to switch on the grammar checker! I was just asking for feedback on the very-much-draft-for-discussion "what to do about warnings" guidelines. Paul --- Paul A. Bristow Prizet Farmhouse Kendal, UK LA8 8AB +44 1539 561830, mobile +44 7714330204 pbristow@hetp.u-net.com
participants (4)
-
Christoph Duelli
-
Christoph Duelli
-
Paul A. Bristow
-
Robert Ramey