On Thu, 20 Oct 2005 14:50:21, Chris Hanson <email@hidden> wrote:
> I said "object" because I'm talking about abstractions. ...
ok
> For example, let's say for the sake of argument that SetFooParameter
> is documented as being thread-safe but FooRef objects are documented
> as not being thread-safe. That means you can call SetFooParameter
> safely from multiple threads without locking but that you can't call
> SetFooParameter on the same FooRef from multiple threads at once,
> period, even with locking. (After all, you may not own all the code
> paths that would need to have locking added to make doing so thread-
> safe.)
The reality might be more complex (or "fine-grained") than that, e.g.:
it might be the case that you can call SetFooParameter on the same
FooRef from multiple threads at once if it is specifically documented
so even if FooRef objects are documented as not thread-safe.
> Thread safety is a tricky issue ...
agree.
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
