Sure,Pavel, after I have a clean build for this module, I get this warning
too, and I have already committed the change and don't find any other
warning..From that,I think my environment on Mac OS X 10.5.8 can identify
the same warning set with yours, but level is still less than yours because
I didn't catch any compile errors caused by these warnings.Before that,for
there are many output logs during build, the warning messages are mixed
among the output info,easily ignored if not leading to compile error. Now,I
use this way "$build > out.txt" to filter other output info and only
warnings left on the screen. Thus, I can get the compile warnings obviously.

I attach my configure parameter for your comparison. If you think this way
is valuable for other developers, could you please composite them and add
to the build guide as "attention items" when doing AOO build, especially
individual module build, to avoid the same issue in the future?Thanks.

./configure --with-dmake-url="
http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.1.tar.bz2"; \
                      --with-epm-url="
http://ftp.easysw.com/pub/epm/3.7/epm-3.7-source.tar.gz"; \
                      --disable-mozilla --disable-build-mozilla
--enable-verbose --enable-category-b \
                      --enable-minimizer --enable-presenter-console
--enable-wiki-publisher --disable-odk

On Tue, Dec 4, 2012 at 3:28 AM, Pavel Janík <pa...@janik.cz> wrote:

> Hi!
>
> On Dec 3, 2012, at 4:18 PM, chengjh wrote:
>
> > I committed some changes to solve the found warnings...Please help to
> > verify again..And I will have a check to the whole sw module to see
> whether
> > any missed warning is still existing.thanks.
>
> thanks. The module is almost clean now.
>
> I only see:
>
> sw/source/filter/ww8/ww8par3.cxx:1125: warning: comparison is always true
> due to limited range of data type
>
> SwNumRule* WW8ListManager::GetNumRule(sal_uInt16 i)
> {
>         if ( i >= 0 && i < maLSTInfos.size() )
>
>
> surely i>=0 when it is unsigned.
> --
> Pavel Janík
>
>
>
>


-- 

Best Regards,Jianhong Cheng

Reply via email to