BorlandTalk.com

Zara · Guest

I am always trying to make my compilations warnnig-free, but with
Borland (BCB6 nad BDS2006) I fail many times. For instance,

W8058 Cannot create pre-compiled header: initialized data in header
appears when including <dinkumware/xlocinfo>, at line 53:
class _CTRIMP2 _Locinfo
{ //...
_Locinfo(const char * = "C"); //...
I am unable to see the initialized data. Am I wrong?

W8026 Functions (...) are not expanded inline
appears very frequently when using boost.
Well, this is expectable, I may turin it off around the boost
header inclusions.

W8027 Functions containing reserved words are not expanded inline
same as W8026.
But it does not appear in Project options |
C++ compiler | Warnings

W8093 Incorrect use of #pragma codeseg.
Never suffered it, but if look at Project options |
C++ compiler | Warnings you will see it has a different syntax
form the rest.

W8091 type.. is an output iterator: input iteartor required
I really hoped to see this warning disappear when it was wrong.
But it hasn't. So much for attention paid to QC by Borland.
What is worse, it does not appear in warning listing, as W8027

W8099 Constant out of range in comparison
I like this warning, I will never disconnect it.
But why is it listed between W8064 and W6066?

Are these matters already covered in some QC report? Should I create
new ones? May I expect them to be solved sometime in the near future?
Or never?

TIA, best regards,

Zara

Zara · Guest

W8066 Unreachable code
It does not appear in warning list.