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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
