Have you tried using Xcode's build settings instead of manually specifying
the compiler flag? There might be more to it than just -fobjc-gc-only.
no, that's the only option needed
if you want to use compiler flags in the long term, it's still worth trying
the build setting, just so you
On Mar 28, 2008, at 04:15, Dominik Pich wrote:
First then I set the GCC Flag: Garbage Collection _required_: -fobj-
gc-only
I coded my cocoa document based application as if there were GC...
no retain/release and no dealloc..
I started and bigidibam... over-releases -- guess something
On Fri, Mar 28, 2008 at 7:15 AM, Dominik Pich [EMAIL PROTECTED] wrote:
Hi,
I started a simple xcode project and wanted to play with GC but cant
get it to work.
First then I set the GCC Flag: Garbage Collection _required_: -fobj-gc-
only
Have you tried using Xcode's build settings instead
On Mar 28, 2008, at 11:20, Dominik Pich wrote:
exactly my point :) there shouldn't be 'any' memory related errors.
GC seems to be OFF like my 2. 'check' showed:
I also added this 'check' to my awakeFromNib
if([[NSGarbageCollector defaultCollector] isEnabled])
NSLog(@GC on);
Where do you have GC enabled? My experience has been that you have to
set it for each target as the project-level setting gets overridden.
On 28-Mar-08, at 11:20 AM, Dominik Pich wrote:
exactly my point :) there shouldn't be 'any' memory related errors.
GC seems to be OFF like my 2. 'check'
On Mar 28, 2008, at 11:42, Robert Douglas wrote:
Where do you have GC enabled? My experience has been that you have
to set it for each target as the project-level setting gets
overridden.
FWIW, I haven't noticed any problem with this on newly-created
projects. But Xcode is so
