It could be [NSFont set] for instance.
probably a bad name for a method :-(
On Aug 24, 2004, at 4:21 AM, Richard Frith-Macdonald wrote:
This mail is an automated notification from the bugs tracker of the project: GNUstep.
/ *********************************************************************** ***/
[bugs #9601] Latest Modifications:
Changes by: Richard Frith-Macdonald <[EMAIL PROTECTED]> 'Date: Tue 08/24/04 at 08:23 (GMT)
What | Removed | Added
----------------------------------------------------------------------- ----
Resolution | None | Invalid
Status | Open | Declined
------------------ Additional Follow-up Comments ----------------------------
Presumably you have a +set method which returns void.
Arguably, the compiler should know that it should use the +set belonging top the NSSet class rather than your other +set method. That's perhaps an issue to take up with the gcc maintainers?
In any case, this is not a base library bug.
/ *********************************************************************** ***/
[bugs #9601] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9601> Project: GNUstep Submitted by: Chad Hardin On: Fri 07/09/04 at 12:46
Category: Base/Foundation Severity: 3 - Ordinary Item Group: Bug Resolution: Invalid Privacy: Public Assigned to: None Status: Declined
Summary: NSMutableSet gcc-3.3.4 compiler error
Original Submission: For some reason I get the following compiler error:
error: void value not ignored as it ought to be
When doing a:
NSMutableSet *set; set = [NSMutableSet set];
when using gcc verson 3.3.4 on i686 and gnustep cvs.
my workaround was to do a:
set = [NSMutableSet setWithCapacity:1];
which worked fine. Strange.
Follow-up Comments ------------------
-------------------------------------------------------
Date: Tue 08/24/04 at 08:23 By: Richard Frith-Macdonald <CaS>
Presumably you have a +set method which returns void.
Arguably, the compiler should know that it should use the +set belonging top the NSSet class rather than your other +set method. That's perhaps an issue to take up with the gcc maintainers?
In any case, this is not a base library bug.
For detailed info, follow this link: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9601>
_______________________________________________ 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
