Re: Draft Proposal for Namespaces in Objective-C

• Subject: Re: Draft Proposal for Namespaces in Objective-C
• From: Jonathan Schleifer <email@hidden>
• Date: Thu, 05 Apr 2012 23:01:43 +0200

Am 05.04.2012 um 18:32 schrieb Kyle Sluder <email@hidden>:

> 2. The first argument to @selector(). Necessary because selectors can exist outside of any namespace. Possibly the most difficult pattern to understand, but hopefully not frequently used—in most cases either a namespace is provided or the argument is omitted.
>
> 3. Using a @namespace() tag inside a message send. Ugly, but the least ugly and least misleading solution I could find for an operation that should be even rarer than creating a non-namespaced selector.

What about namespace.selector?

[obj some.namespace.fooWithBar: bar];
[obj performSelector: @selector(some.namespace.fooWithBar:)];

Then it would at least be consistent ;).

--
Jonathan
(vom iPad gesendet)
 _______________________________________________
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

• Follow-Ups:
  • Re: Draft Proposal for Namespaces in Objective-C
    • From: Charles Srstka <email@hidden>
  • Re: Draft Proposal for Namespaces in Objective-C
    • From: Kyle Sluder <email@hidden>

• Prev by Date: Re: Draft Proposal for Namespaces in Objective-C
• Next by Date: Re: Draft Proposal for Namespaces in Objective-C
• Previous by thread: Re: Draft Proposal for Namespaces in Objective-C
• Next by thread: Re: Draft Proposal for Namespaces in Objective-C
• Index(es):
  • Date
  • Thread