Re: Failure on unarchiving a NSBezierPath
Re: Failure on unarchiving a NSBezierPath
- Subject: Re: Failure on unarchiving a NSBezierPath
- From: Jens Alfke <email@hidden>
- Date: Mon, 28 Apr 2008 17:03:12 -0700
On 28 Apr '08, at 8:56 AM, Kyle Sluder wrote:
Not necessarily true in the general case. The semantics of buffered
output may interfere, especially if instead of just sending
unrecognized selectors to a random object the code were sending
messages to a pointer off in la-la land. It's always a nightmare to
watch students toss printf() everywhere in their C code in an attempt
to figure out where the program is crashing and then not see messages
they know should be displayed.
That can happen with printf, or other calls that write to stdout; but
stderr is unbuffered, so output will show up right away (and in
correct order.) NSLog writes to stderr, as does all other properly-
written logging code.
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden