• 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: What's with these redundant methods ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What's with these redundant methods ?


  • Subject: Re: What's with these redundant methods ?
  • From: MarketLogix Developer <email@hidden>
  • Date: Tue, 22 Apr 2003 18:10:00 -0700

On Tuesday, April 22, 2003, at 04:21 PM, Lloyd Dupont wrote:

I do protest, GNUstep implement NSObject as well ! as does NeXTSTeP 3.3 ! (or 4.3, my memory is not what it used to be :-)
and the retain/release mechanism is a very usefull addition !

I believe that NSObject was introduced with the OpenStep product where the last release was 4.2. NeXTStep
sports Object ALONE as the root much in the form that still lives on in the Gnu runtime. Ah yea, retain/release,
maybe I'll get around to checking those out sometime. Still really haven't found the need as I'm old school and
fairly adept at memory management.

I always assumed NSObject was created more for FoundationKit specific support. And the notion that NeXT/Apple
had dug back and rearchitected an elegantly simple root class was always something of a turn off for me so I could
never really bring myself to look at it. The runtime and Object class should have no notion of GUI widgets.
Maybe that's the way NSObject still is, like I said, I'm happy with Object so I never looked.


In fact, while I'm at it, why is there an NSObject ?

because of this new memory policy (retai/release), and some other thing and to let all code wrok erfectly without being perturbated by these breaking change in the root object ....

Ummm, O.K. but back to my original Q, what was wrong with Object's methodFor: and respondsTo: . Why create 2 new
methods, methodForSelector: and respondsToSelector:, that do EXACTLY the same thing in NSObject ? Is it for
namespace clashes ? Is anyone likely to use both the Object and NSObject class in the same App ?

-----------------------------------------------
bisk ~ OSX.2.4
G4 PowerMac Gigabit, Dual 500
Sony SDM-M81 18.1" LCD display
1GB, 40GB, SuperDrive(DVR 105)
HP "All-in-One" d135 BubbleJet
-----------------------------------------------
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: What's with these redundant methods ?
      • From: Lloyd Dupont <email@hidden>
References: 
 >Re: What's with these redundant methods ? (From: Lloyd Dupont <email@hidden>)

  • Prev by Date: Re: -2856 error code
  • Next by Date: Re: multiple table views
  • Previous by thread: Re: What's with these redundant methods ?
  • Next by thread: Re: What's with these redundant methods ?
  • Index(es):
    • Date
    • Thread