FROM : Hamish Allan
DATE : Thu Feb 28 23:31:40 2008
Hi,
The GNUstep documentation for the
NSObject(NSMainThreadPerformAdditions) category states the following
for performSelectorOnMainThread: withObject: waitUntilDone: modes:
"Where this method has been called more than once before the runloop
of the main thread runs in the required mode [i.e., with
waitUntilDone:NO], the order in which the operations in the main
thread is done is the same as that in which they were added using this
method."
[additions mine]
However, there is no equivalent promise in Apple's documentation for
NSObject; it is conspicuous in its absence. Can anyone confirm or deny
that it has the same behaviour as in GNUstep?
(This question was previously asked on this list in 2006
(http://lists.apple.com/archives/cocoa-dev/2006/Feb/msg01215.html),
but I can find no answer to it in the archives.)
Thanks,
Hamish
DATE : Thu Feb 28 23:31:40 2008
Hi,
The GNUstep documentation for the
NSObject(NSMainThreadPerformAdditions) category states the following
for performSelectorOnMainThread: withObject: waitUntilDone: modes:
"Where this method has been called more than once before the runloop
of the main thread runs in the required mode [i.e., with
waitUntilDone:NO], the order in which the operations in the main
thread is done is the same as that in which they were added using this
method."
[additions mine]
However, there is no equivalent promise in Apple's documentation for
NSObject; it is conspicuous in its absence. Can anyone confirm or deny
that it has the same behaviour as in GNUstep?
(This question was previously asked on this list in 2006
(http://lists.apple.com/archives/cocoa-dev/2006/Feb/msg01215.html),
but I can find no answer to it in the archives.)
Thanks,
Hamish
| Related mails | Author | Date |
|---|---|---|
| Hamish Allan | Feb 28, 23:31 | |
| Kyle Sluder | Feb 28, 23:48 | |
| Hamish Allan | Feb 29, 00:03 |






Cocoa mail archive

