Hmm ... I started reclassifying these as category ';change request'
rather than 'bug' and severity 'wish' rather than 'normal' since
these are plainly not bugs, just (mostly) spurious compiler warnings.
However, I'm not sure that's the right thing to do ...
Should they be closed as 'invalid' instead? I'm inclined to think it
would be nice to change code to avoid spurious compiler warnings as a
very low priority issue, but perhaps others feel different?
On 4 Jul 2006, at 17:01, Patrick McFarland wrote:
URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=16997>
Summary: compiler warning for NSZone.m
Project: GNUstep
Submitted by: diablod3
Submitted on: Tuesday 07/04/2006 at 16:01
Category: Base/Foundation
Severity: 3 - Normal
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
NSZone.m: In function ‘default_stats’:
NSZone.m:535: warning: ‘dummy.bytes_free’ is used uninitialized in
this
function
NSZone.m:535: warning: ‘dummy.chunks_free’ is used uninitialized in
this
function
NSZone.m:535: warning: ‘dummy.bytes_used’ is used uninitialized in
this
function
NSZone.m:535: warning: ‘dummy.chunks_used’ is used uninitialized in
this
function
NSZone.m:535: warning: ‘dummy.bytes_total’ is used uninitialized in
this
function
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=16997>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
