Hi, > If you want static stuff in CFCs you can set variables within the > component but outside of any function definitions.
Ah yes. That makes sense. > Foo will become available to all functions in the component, but not to > any components that extend it. That sucks. > If you want to do the equivalent of super.x in CF, you basically can't > for variables, but you can for functions. Pity. In java you can use super.x to access a componants super classes variable, this.x and x would refer to the calling cfc local variables. Called shadowing in stuff I've read. > Say you have a method in component1 and you rewrite that method in > component2. You can still get to the method from component1 by using > this.methodname() instead of methodname(). I have no idea if this is a > bug or a feature though. and this makes it more weird. In java you can't access an overridden method in a superclass, even using super.x(). What is even odder is that this.methodname() refer to a superclasses method! Sure this is right? > Not being a Java developer, my answers might be a little off here, but > for what it's worth: > Spike Always a pleasure spike :-) -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
