Re: printf
Re: printf
- Subject: Re: printf
- From: John Stiles <email@hidden>
- Date: Fri, 14 Dec 2007 09:51:43 -0800
In my experience, if two threads are calling printf at once, their
output can be arbitrarily interleaved. It's not unstable, but it can be
a little goofy.
Richard Somers wrote:
What about this stated functionality of NSLogv from Apple's
documentation.
"Output from NSLogv is serialized, in that only one thread in a
process can be doing the writing/logging described above at a time.
All attempts at writing/logging a message complete before the next
thread can begin its attempts."
"The effects of NSLogv are not serialized with subsystems other than
those discussed above (such as the standard I/O package) and do not
produce side effects on those subsystems (such as causing buffered
output to be flushed, which may be undesirable)."
Does a printf provide this or is this something to worry about? I just
finished writing my own simple replacement for NSLog several days ago
using printf and was wondering if I was going to run into problems
down the road.
Richard
On Dec 13, 2007, at 8:03 AM, Clark Cox wrote:
No, but it's relatively easy to write your own:
_______________________________________________
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
_______________________________________________
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
| References: | |
| | >printf (From: Roland Silver <email@hidden>) |
| | >Re: printf (From: "Clark Cox" <email@hidden>) |
| | >Re: printf (From: Richard Somers <email@hidden>) |