AFAIK, until Java, there really wasn't a mainstream, statically typed, non-interpreted language which allowed for this directly.
A fragile hack was to find out the memory locations and access them directly. but this is much more extreme than what we are talking about here. Dynamic types, virtual machines, and interpreters all tend to carry around the very information needed to make this magic work. Kudos to Java for exposing this in a useful manner. --- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote: > > How people handle these situations in other languages? > > Apparently, the implied path is extending the base components if you don't > like them. That seems... more restrictive. Again, what do other languges & > frameworks do? I have no problem with extending base components, and in I fact I prefer that method assuming it's not too verbose. But realize that in many cases the API still may not allow for overiding the object you need in practice. For example API's which have object factories can be problematic unless the API also opens up the factory mechanism in some way. Worst case you need to reimplement not just the overidden methods, but the entire stackj above the factory call. ------------------------ Yahoo! Groups Sponsor --------------------~--> 1.2 million kids a year are victims of human trafficking. Stop slavery. http://us.click.yahoo.com/.QUssC/izNLAA/TtwFAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
