Re: What's with these redundant methods ?
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:21:17 -0700
On Tuesday, April 22, 2003, at 04:40 PM, John C. Randolph wrote:
My question was more "why were these reimplemented in NSObject" ?
To conform to the new method naming guidelines, which call for more
descriptive names, eg: -performSelector:withObject: instead of
-perform:with:, or
O.K., I'll drink to that but are we saying that Object is slated to go
away ?
In fact, while I'm at it, why is there an NSObject ?
Mostly to avoid breaking existing NeXTSTEP code.
Yep, I see that now, out with old, in with the new.
Object was lacking in many ways, the main one being that it's only
memory management were the +alloc and -free methods. To implement
distributed objects, we needed to have reference counting and adding
it to Object really wasn't feasible.
I understand the addition of the retain/release stuff but DO existed in
NeXTStep long before there existed
OpenStep or NSObject. I know, because I still have at least one
NeXTStep v3.3 DO server running out there.
If I remember right, the reference counting stuff was handled in
NXProxy or something.
-----------------------------------------------
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.