Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New ObjC style language development




2005/08/22 v 8:54, ObjM2:


On Aug 22, 2005, at 6:40 AM, Jens Ayton wrote:


How about "ALTERS"?


It's a question of whether to pick "addition" or "modification".

If "modification" was to be the emphasis, then perhaps "MODIFIES" would be best. Anyway, thanks for the feedback, we're going to revisit this again.

Not only I'm just an ordinary Cocoa developer, I'm also a non-native speaker, so my opinion may not weigh much, but ALTERS sounds better for me. Let's see what Webster has to say about these two words:


ALTER implies a difference in some particular respect without suggesting loss of identity <slightly altered the original design>.

MODIFY suggests a difference that limits, restricts, or adapts to a new purpose <modified the building for use by the handicapped>.

Why would you choose modify? (Well, I know it's longer;).)

- variables declared after PUBLIC TO NEIGHBORS makes them visible only within the enclosing module and classes also defined within that enclosing module

What we don't like about this is the fact that it is not an internationally acceptable solution because of the US American spelling of NEIGHBORS.

PUBLIC TO MODULE seems to be a pretty stratithforward solution.


Also, a nitpick: the Interface sample contains:

CLASS METHOD initWithFoo: (foo : Foo) andBar: (bar : Bar) : FooBar;

According to Cocoa/OpenStep practice, init* should be an instance method. The corresponding class method would be newWithFoo:andBar:, or fooBarWithFoo:andBar: if it autorelease the return value. Also, the return type should be OBJECT to allow clean overriding of superclass initialisers with the same name.


Indeed. However, keep in mind that the wiki page intends to present an overview and be concise. To the Modula-2 programmer the concept of dynamic typing is foreign and thus for illustrative reasons it was important to show that the method returns Foobar the class.

I think it returns an instance of Foobar. Returning a class or an instance has nothing to do with the fact whether it's a class or instance method.


For example both +class and -class return the receceiver's class (not an instance), but this is never the case of +alloc, -init or +new.


The only reason why initWithFoo:andBar: is presented as a class method is to show that there is a syntactical destinction between class methods and instance methods, a concept that will again be foreign to Modula-2 and Pascal programmers. But the idea to use newWithFoo:andBar: as an example instead is great. We'll change that. Thanks a lot for your feedback.

I think we're getting into details here and that this should rather go to a ObjM2-specific mailing list. Are there any plans to start such a list?


--
Adam Nohejl
Loki Software
mailto:email@hidden
http://lokisw.com



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/objc-language/email@hidden

This email sent to email@hidden
References: 
 >New ObjC style language development (From: ObjM2 <email@hidden>)
 >Re: New ObjC style language development (From: Adam Nohejl <email@hidden>)
 >Re: New ObjC style language development (From: ObjM2 <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.