Re: NEWERA - beforerow -- supertable class

In article <33D7A2FD.6D3@informix.com>, Dennis Pimple <dennisp@informix.com> writes >Mike Ripley wrote: > >> > >> I would like to thank everyone for their help on this subject, but all >> the solutions still require the developer to be aware of the event >> functionallity of the parent class. Either you remember to override a >> function or you remember to make a call in the child event. >> >> Whilst I am now resigned to using one of the two methods surely this is >> contrary to the concept of inherited functionally through the class >> structure? > >I disagree. The concept of being able to override inherited >functionality is basic to object orientation. (If I have inherited black >hair and decide to dye it blonde, I better know what benefits of black >hair I'm losing.) > >Which emphasises the need for complete documentation on derivable >classes; make sure you inform the consumer what events/methods of a bas >class (like ixSuperTable) you're overriding in your class, so they can >be aware and take appropriate step. > > > > >//////////////// ======================================================= >////////// // Dennis J. Pimple Informix Software, Inc. I take it from your reply that there is no other way of overcoming the need to refer to the parent class in my example. I like your reference to the need for complete documentation. Please send me a short list of all the companies who have complete documentation, keep it completely up to date and always refer to it religiously whenever information is required about programs and systems. I can give you a very long list of companies who say they do! In our company we are attempting to migrate to a paperless office so we expect programming languages to be mainly self documenting. However I will take your advice and suggest that anyone using derived classes check the code of the parent class to determine the full functionality and to include code in the child task to supplement functionality from the parent. -- Mike Ripley