The bit that doesn't work is the bit where you're supposed to be able to call a superclass method.
The code I was sent has this.constructor() being called from the child. Since it doesn't actually overload the constructor method it would obviously be using the method from the parent. Spike p.s. I'm doing many cool things with CFCs. Drop me a line off list. > -----Original Message----- > From: Justin MacCarthy [mailto:[EMAIL PROTECTED]] > Sent: 19 September 2002 17:41 > To: [EMAIL PROTECTED] > Subject: RE: [ cf-dev ] 2 cfc questions > > > OH Which bit ? what code? Calling a superclasses method? > > I've writing up a paper on advanced cfc usage and a > comparison of java v's cfcs. Anyone doing anything cool with > cfcs let me know :-) > > Justin > > > -----Original Message----- > > From: Spike [mailto:[EMAIL PROTECTED]] > > Sent: 19 September 2002 16:31 > > To: [EMAIL PROTECTED] > > Subject: RE: [ cf-dev ] 2 cfc questions > > > > > > actually scratch that super.x stuff... > > > > I just tested the code that was supposed to prove it and it > turned out > > to be rubbish. > > > > Spike > > > > > -----Original Message----- > > > From: Spike [mailto:[EMAIL PROTECTED]] > > > Sent: 19 September 2002 17:21 > > > To: [EMAIL PROTECTED] > > > Subject: RE: [ cf-dev ] 2 cfc questions > > > > > > > > > Not being a Java developer, my answers might be a little > off here, > > > but for what it's worth: > > > > > > If you want static stuff in CFCs you can set variables within the > > > component but outside of any function definitions. > > > > > > i.e. > > > > > > <cfcomponent> > > > <cfset foo = 'bar'> > > > <cffunction name="nuffin"> > > > <cfset nuffin = 'fun'> > > > </cffunction> > > > </cfcomponent> > > > > > > Foo will become available to all functions in the > component, but not > > > to any components that extend it. > > > > > > If you want to do the equivalent of super.x in CF, you basically > > > can't for variables, but you can for functions. > > > > > > 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. > > > > > > Spike > > > > > > > -----Original Message----- > > > > From: Justin MacCarthy [mailto:[EMAIL PROTECTED]] > > > > Sent: 19 September 2002 16:57 > > > > To: [EMAIL PROTECTED] > > > > Subject: [ cf-dev ] 2 cfc questions > > > > > > > > > > > > I just what to clarify some cfc questions. > > > > > > > > Is there an equivalent of a Java Class fields (static) in cfcs? > > > > > > > > How can you refer to a superclasses variable from a > sub class ? > > > > E.G. super.x in java (shadowed fields) > > > > > > > > Thanks J > > > > > > > > > > > > -- > > > > ** 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] > > > > > > > > > > > > > > > > > > > > -- > > > ** 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] > > > > > > > > > > > > > > -- > > ** 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] > > > > > > > > > -- > ** 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] > > -- ** 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]
