On 04.04.2012, at 21:44, Kyle Sluder wrote:
> This proposal is currently a draft, and might have some rough edges,
> particularly in the area of the @namespace and @using directives. I
> welcome your comments and criticisms, and I hope the ensuing discussion
> can produce a sensible and useful namespace implementation.
that looks great, thanks for sharing this and getting the ball rolling. A few things I noticed while reading, in no particular order:
-> You should remove the semicolon in the method definitions (samples). Makes it easier to read intent. Also, @selector(key1:key2) is missing its second ":".
-> Also, selectors don't really have "keys". I think they're usually called "labels", although they're strictly not even that.
-> Also, why not use "." as the separator in @selector ? I.e. @selector(default.intValue) instead of @selector( default, intValue )
-> Also, not sure I understand the "Namespaced Classes, Categories, and Protocols" section's restriction of one namespace per protocol. Does that cover protocols that conform to other protocols in different namespaces?
-> Oh, and you wrote "expose publicly expose" there.
-> "[<receiver> @namespace(<ns>) arg1:... arg2:...];" I wonder if we could parse [<receiver> ns.arg1: ... arg2: ...]; ? Or use :: ?
-> Another typo "namespaces differently".
And now on to read all those other peoples' comments :-)
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
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