> Yuck... :)
I was intending to indicate a short-term solution with existing delphi for the proposed
scenario of subclassing. ;)
> Is the IDE too responsive for you, Aaron? :) Ooh... invites flames...
> best change subject... well, you did mention that "J" word. :)
> Come on everyone, haven't any of you ever wanted to subclass a component
> on a form without either sticking yet another
> "TAnotherSubclassedComponentThatsNeededForOneParticularFormButICouldntTe
> llYouWhyOrWhatItDoesWithoutLookingAtItAgain" component into the
> component palette, or creating and keeping track of "helper objects"?
I don't know that performance loss should be that large if a similar scheme of an
intermediate bytecode were used. The benefits would be great but bear in mind
that this is a complete rewrite and redesign of delphi for Borland and will not
happen...
> One of the advantages of my suggestion is that it would be very easy to
> implement. One tiny extra situation to check for during a compile and a
> slight relaxing of the loading rules - that's it! :)
I'm not convinced that the proposed concept provides an elegent solution but it has
been
placed on the wishlist so others can feel free to add addenda and vote.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
