• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Java vs. Objective-C for Cocoa
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java vs. Objective-C for Cocoa


  • Subject: Re: Java vs. Objective-C for Cocoa
  • From: Ondra Cada <email@hidden>
  • Date: Sun, 24 Apr 2005 00:30:22 +0200

Marcel,

(cannot argue about Smalltalk -- did not used the thing myself for too many years, forgot too much. Perhaps Smalltalk uses better paradigms for metaprogramming than Cocoa, I would not argue that. May you perhaps show us what Smalltalk uses instead of, say, Cocoa bindings, and how it gets automatically re-factored?)

On 24.4.2005, at 0:13, Marcel Weiher wrote:
I don't really see your point here. Certainly something like HOM is largely transparent to refactorings (maybe apart from the __ trick it needs for another couple of days...)

Yes and no. In theory, HOM does not bring (almost) anything new to the "refactoring problems area". It, though -- and do please correct me if I am overlooking something important -- considerably emphasizes many of them which, in non-HOM environment, stay more or less latent.


An actual example: although the functionality is available for a long long time, it is not too common to use a code like

[array makeObjectsPerformSelector:@selector(whatever)]; //1

and I daresay it is betwixt Cocoa programmers rather common to write the explicit code of kind

for (NSEnumerator *en=[array objectEnumerator],Foo *foo;foo=[en nextObject];) [foo whatever]; //2

On the other hand,

[[array each] whatever]; //1

is extremely common with HOM, being almost an archetypal HOM example.

I may be wrong (well I was often enough in the past), but I cannot see a reasonable re-factoring algorithm for "whatever" in those //1 cases, due to the fact Cocoa containers are completely typeless. That in //2 the re-factoring tool can do much better is self-evident.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Java vs. Objective-C for Cocoa
      • From: Marcel Weiher <email@hidden>
References: 
 >Java vs. Objective-C for Cocoa (From: "Zacharias J. Beckman" <email@hidden>)
 >Re: Java vs. Objective-C for Cocoa (From: Rick Kitts <email@hidden>)
 >Re: Java vs. Objective-C for Cocoa (From: John Stiles <email@hidden>)
 >Re: Java vs. Objective-C for Cocoa (From: "Zacharias J. Beckman" <email@hidden>)
 >Re: Java vs. Objective-C for Cocoa (From: Rick Kitts <email@hidden>)
 >Re: Java vs. Objective-C for Cocoa (From: Ondra Cada <email@hidden>)
 >Re: Java vs. Objective-C for Cocoa (From: Marcel Weiher <email@hidden>)

  • Prev by Date: Re: Java vs. Objective-C for Cocoa
  • Next by Date: Re: Java vs. Objective-C for Cocoa
  • Previous by thread: Re: Java vs. Objective-C for Cocoa
  • Next by thread: Re: Java vs. Objective-C for Cocoa
  • Index(es):
    • Date
    • Thread