Ticket #6486 (new defect)

SVN Diffs for #6486

 

Opened 3 weeks ago

Last modified 3 weeks ago

make --enable-strict configure option be default

Reported by: andy Assigned to: srl
Priority: assess Milestone: UNSCH
Component: config_build Version:
Keywords: Cc:
Load: Xref:
Java Version: Operating System:
Project (C/J): ICU4C Weeks:
Review:

Description

Change the default configure option to have --enable-strict to help avoid checking in code with portability problems.

Do something similar for Windows project files, crank up the warning levels.

Attachments

Change History

08/06/08 13:33:07 changed by grhoten

This option is off by default for a reason. The strict option has some significant problems between compiler versions. Some harmless warnings become errors with this option, like the trailing semicolon after a class definition. Some warnings appear and disappear depending on the version of gcc.

On some platforms, like Cygwin, this option can spew thousands of worthless warnings depending on the brokenness of the gcc version on that platform at the time.

Some system headers, like windows.h and others, can't properly handle the increased strictness.

For developers, this is an excellent option to use. For a formal release of ICU, it's counterproductive for users compiling ICU. It should be strict for developers and lenient for the users.


Add/Change #6486 (make --enable-strict configure option be default)




Anti spam check: