After some study, I will first try the luni module. And I will:
1.Open all warnings on linux platform. 2.Clean up any warning for GCC 3.0 or 4.0. 3.Set warning-as-error by default. 4.Considering the behaviors of different compilers on different platforms, I can hardly treat with all these compilers in the first time. So an build option hy.no.warning can be set to avoid warning-as-error if necessary. A JIRA https://issues.apache.org/jira/browse/HARMONY-3752 is reported for the issue. On 4/24/07, Leo Li <[EMAIL PROTECTED]> wrote:
OK, Tim. I will begin to clean up warnings.:) On 4/24/07, Tim Ellison <[EMAIL PROTECTED]> wrote: > > Leo Li wrote: > > OK, I will try to open them. > > > > But there is one thing to decide: whether to regard all warnings as > > error. I once opened all warnings as error in luni module but the > config is > > changed to just report warning but does not stop compiling. If the > warning > > is not regarded as error as on win32 platform does, the different > building > > behavior will occur. > > So if no body objects, I will use the strict form, that is -Wall > -Werror > > option for GCC 3.0 or GCC 4.0. > > IIRC we had the strict options set for a while, then took in a bulk > contribution that required we were a bit more forgiving during > integration. It would be good to tidy up all the code to avoid > warnings. > > Regards, > Tim > -- Leo Li China Software Development Lab, IBM
-- Leo Li China Software Development Lab, IBM
