On Apr 5, 2012, at 23:05, Kyle Sluder wrote:
> On Apr 5, 2012, at 2:01 PM, Jonathan Schleifer wrote:
>> What about namespace.selector?
>> [obj some.namespace.fooWithBar: bar];
>> [obj performSelector: @selector(some.namespace.fooWithBar:)];
>> Then it would at least be consistent ;).
> See previous discussion: how do you create a selector that is not attached to a namespace?
@selector(*.foo), by vague analogy to globbing? It’s new magic punctuation, but I think it’s clearer than @selector(nil, foo) – it’s at least obvious that it’s something different from a name, if not what it actually is.
On Apr 5, 2012, at 22:15, Remy Demarest wrote:
> Before adding namespace, I would think that's a better idea to first add real @private/@protected/@package methods in ObjC.
As far as I can see, providing any sort of actual protection to @private methods in the face of dynamic dispatch would require a mechanism analogous to anonymous (or undeclarable) namespaces. Making the compiler and runtime changes necessary to support this without also providing for namespaces seems pointless.
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden