|
From: | Ziemowit Laski |
Subject: | Re: PATCH: Merge objc-improvements-branch to mainline |
Date: | Thu, 25 Sep 2003 14:10:23 -0700 |
On Thursday, Sep 25, 2003, at 10:10 US/Pacific, Alexander Malmberg wrote:
Ziemowit Laski wrote:On Wednesday, Sep 24, 2003, at 12:09 US/Pacific, Ziemowit Laski wrote:[snip](Additionally, the documentation for @synchronize is very vague.)I'm certainly open to suggestions as to how to improve this.Well, it occurred to me that one obvious way of improving things is to describe_what_ @synchronized acutally does :-) :-), and so I added a paragraph.So, here is the improved documentation:[snip]This is better, but it still doesn't say how the 'guard' object is used.Is the guard object supposed to respond to any particular messages (if so, which messages, and what happens if one of them causes an exception to be raised?), or can the runtime lock on arbitrary objects (if so, what is the behavior wrt recursive locking)?
No, the guard object does not need to be special in any way. As for recursive locking, I honestly don't know, but it's a very good questionwhich I'll forward to our runtimes group (and will update the documentation
with the response I get).BTW, can you re-spin your patch (examining root instance methods when sending messages to 'Class') against the mainline now that all the stuff is in? Thanks.
--Zem -------------------------------------------------------------- Ziemowit Laski 1 Infinite Loop, MS 301-2K Mac OS X Compiler Group Cupertino, CA USA 95014-2083 Apple Computer, Inc. +1.408.974.6229 Fax .5477
[Prev in Thread] | Current Thread | [Next in Thread] |