On 6/15/06, Mark Lapasa <[EMAIL PROTECTED]> wrote:
Thx Ian, the only thing I can think of as an argument is Marker Interfaces. Then again, I think I might just be using using interfaces the wrong way as I am trying to establish some form of polymorphism in trying to access both foo() and bar() methods.
Hm. If you're using marker interfaces just to note that specific objects are to be treated in a specific way, then you probably don't need to be downcasting anyway - as putting a marker interface (which inherently contains no function signatures) on something doesn't guarantee that that object has any particular behaviour as far as methods goes. It's just a signal to some containing code of some sort that you're allowed to do particular things to that object - to take a Java example, implementing Serializable means that the containing code is allowed to walk through the object's fields and store each one in a 'standard' way. There are no guarantees about methods, so downcasting and calling a method is a bit peculiar. But anyway, I'm waffling now - without knowing what you're trying to do, I can't really offer any alternatives to your current design. :-) Cheers, Ian _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
