I would say to keep the selector namespacing for later, this is a completely different matter and I don't think you'd implement it the same way.
Namespacing classes and protocols should be less of a headache than the namespacing selectors.
Remy "Psy" Demarest
Le 12 avr. 2012 à 10:18, Kyle Sluder a écrit :
> On Apr 12, 2012, at 4:05 AM, Ian Joyner <email@hidden> wrote:
>
>> Part of my unease is that the disambiguation in other languages I have seen (like Java) occurs in the code all over the place, particularly with com.mikeash.Array. Really, the dots (.), might look like some kind of multi-level name, but in actual fact are just part of a longer name.
>>
>> A single point of decision would be much cleaner, like a single piece of meta syntax saying
>>
>> use array from com.mikeash
>>
>> or with renaming
>>
>> use array from com.mikeash as maarray
>
> This is covered in my proposal by using namespace scopes. You add "@using com.mikeash" to the top of the file and now naked references to Array resolve to com.mikeash.Array. Or to avoid clashes you use "@using com.mikeash = ma" and now you can use ma.Array.
>
> --Kyle Sluder
> _______________________________________________
> 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
_______________________________________________
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
