Re: Redeclaring overrides
Re: Redeclaring overrides
- Subject: Re: Redeclaring overrides
- From: Chris Gehlker <email@hidden>
- Date: Sat, 18 Aug 2001 19:00:35 -0700
On 8/18/01 3:14 PM, "Georg Tuparev" <email@hidden> wrote:
>
Short answer: readability. One should always assume that the cowboy
>
style of lonely hacking is a thing of the past ... or am I dreaming
>
again?
Well, that's just too short, at least for me. If there were a style that
said "Declare everything you define, even if it's an override" I could
understand. But that's not what "Learning Cocoa" is doing.
If there were a style that said "Declare everything that you override if
it's not likely that most applications will override that method I could
understand that as well. But awakeFromNib?
Furthermore the book declares awakeFromNib in exactly one sample program and
overrides it in many.
I'm still very confused.
>
On Saturday, August 18, 2001, at 08:54 PM, Chris Gehlker wrote:
>
>
> Toward the end of "Learning Cocoa" there is some advice to declare
>
> awakeFromNib and isOpaque in the .h file of a sample application. The
>
> book
>
> doesn't go into any detail about why you should redeclare methods that
>
> are
>
> already in the headers. It certainly doesn't do this consistently.
>
>
Georg Tuparev
>
Tuparev Technologies
>
Klipper 13
>
1186 VR Amstelveen
>
The Netherlands
>
Mobile: +31-6-55798196
>
--
Some people say Windows users have an inferiority complex.
That's not true. It's not a complex.