Amen to that Magnus - what possible motive can there be to fix invisible,
benign 'problems' ?
--
Dave Pointon FIAP MBCS
Now I saw, tho' too late, the folly of beginning a work before we count the
cost and before we we judge rightly of our strength to go thro' with it -
Robinson Crusoe
On 3 Decem
On Dec 3, 2014, at 3:09 AM, Magnus Ihse Bursie
wrote:
> On 2014-12-02 22:59, Jonathan Gibbons wrote:
>> Build folk,
>>
>> The build has always generated warnings (sigh!) but right now, the warnings
>> look scarier than usual.
>>
>> In particular, when the build terminates, I get a couple of
On 12/03/2014 03:09 AM, Magnus Ihse Bursie wrote:
On 2014-12-02 22:59, Jonathan Gibbons wrote:
Build folk,
The build has always generated warnings (sigh!) but right now, the
warnings look scarier than usual.
In particular, when the build terminates, I get a couple of
screenfuls of messages
On 03/12/2014 07:58, Staffan Larsen wrote:
These are warnings in the java.desktop module. I don’t know what the
appropriate email list is for java.desktop discussions, but perhaps bringing it
up there would be the right thing to do?
Most of the warnings that I see are in the AWT and 2D code an
On 2014-12-02 22:59, Jonathan Gibbons wrote:
Build folk,
The build has always generated warnings (sigh!) but right now, the
warnings look scarier than usual.
In particular, when the build terminates, I get a couple of screenfuls
of messages like this:
/w/jjg/work/jfm2.0/dev.8059977.sjfm/jd
These are warnings in the java.desktop module. I don’t know what the
appropriate email list is for java.desktop discussions, but perhaps bringing it
up there would be the right thing to do?
/Staffan
> On 2 dec 2014, at 22:59, Jonathan Gibbons wrote:
>
> Build folk,
>
> The build has always g
Great. I'll close the bug I filed as a dup of this one then.
Thanks
Michael
On 10/02/14 10:39, Chris Hegarty wrote:
On 08/02/14 00:41, Mike Duigou wrote:
Part of the issue seems to be that the meaning of -Wno-unused seems
to have changed and/or become ineffective. It's reported that it
prev
On 08/02/14 00:41, Mike Duigou wrote:
Part of the issue seems to be that the meaning of -Wno-unused seems to have
changed and/or become ineffective. It's reported that it previously hid all
unused parameter warnings though it doesn't seem to on any compiler I'm
currently using.
I've included
Part of the issue seems to be that the meaning of -Wno-unused seems to have
changed and/or become ineffective. It's reported that it previously hid all
unused parameter warnings though it doesn't seem to on any compiler I'm
currently using.
I've included -Wno-unused-parameter with the changes g
On 07/02/14 10:43, Michael McMahon wrote:
It seems, the warning is emitted by the combination of:
-W -Wall
and could be disabled by adding -Wno-unused-parameter
Given the definition of JNI method signatures, then I agree with this.
It would be really helpful to be able to see "real" warnings
It seems, the warning is emitted by the combination of:
-W -Wall
and could be disabled by adding -Wno-unused-parameter
Michael
On 07/02/14 10:06, Dmitry Samersoff wrote:
Michael,
I'm totally agree with you (and had sent to build-dev approx the same
letter about two weeks ago).
On my opinion
Michael,
I'm totally agree with you (and had sent to build-dev approx the same
letter about two weeks ago).
On my opinion we should turn off unused parameter warning, at least for
product build.
-Dmitry
On 2014-02-07 14:02, Michael McMahon wrote:
> Just wondering is there a plan to deal with b
12 matches
Mail list logo
