Re: NSUserDefaults and the synchronize: method - doesn't seem to sync...
Re: NSUserDefaults and the synchronize: method - doesn't seem to sync...
- Subject: Re: NSUserDefaults and the synchronize: method - doesn't seem to sync...
- From: Andreas Monitzer <email@hidden>
- Date: Mon, 3 Dec 2001 16:26:43 +0100
On Monday, December 3, 2001, at 12:39 , Diggory Laycock wrote:
Well, my address is @cocoadevcentral.com, not @fucktheAPIscentral.com.
Btw,
I started programming the Classic API (which became the Carbon API)
and moved to Cocoa afterwards.
Sorry, I really didn't mean to offend - I personally am not that
familar with classic/carbon and prefer to stick to cocoa as much as I
can.
I don't feel offended at all.
I was under the impression that it was valid to alter these defaults
using cocoa. Because of this I was surprised that someone who helps
people learn cocoa would suggest using carbon over cocoa!
Don't believe the Apple diagrams - there's nothing like the "Carbon
World" and the "Cocoa World" on Mac OS X/MachO. There are APIs that use
different languages (C, C++, Java, ObjC, Perl, TCL...), and there are
several event handling mechanisms (CFRunLoop/NSRunLoop, Carbon Events,
WaitNextEvent, select, AWT). Some things only work in specific event
mechanisms (Carbon Hotkeys need Carbon Events for example), but
everything else can be (and sometimes has to be) mixed.
Generally, you should always use the commands with the highest level of
abstraction that includes all features you need - those are less likely
to change or do harm.
andy