[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #25553] gui bug when build with mingw32, with garbage collection
|
From: |
matt rice |
|
Subject: |
[bug #25553] gui bug when build with mingw32, with garbage collection |
|
Date: |
Wed, 11 Feb 2009 04:18:06 +0000 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 |
Follow-up Comment #1, bug #25553 (project gnustep):
I don't understand,
DESTROY is already defined differently based on if
GS_WITH_GC is defined or not, wasn't the point of all these macros so that
they could be enabled and disabled based on if GC was there or not.
DESTROY is defined as (object = nil)
if GS_WITH_GC is enabled
and
id __o = object;
object = nil;
[__o release];
if GS_WITH_GC is not enabled,
why do we need another set of macros on top of that?
is IF_NO_GC somehow different than GS_WITH_GC?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25553>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/