If you do this:
cfset var s = structNew()
cfset s = mystruct
Then s is not a struct, but a pointer to mystruct, so whenever you set a
property of s, you are in fact setting a property of mystruct.
Also, personally, theres no way i would do this:
cfif NOT isDefined(mystruct)cfset
Kerry,
Thanks for your help. You're certainly right about the duplicate
function...and of course I should have known that already.
But I'm a little confused about your statement that I shouldn't do this:
cfif NOT isDefined(mystruct)cfset this.init()/cfif
I could call any function in my
: cfcomponent/function inheritence issue?
Kerry,
Thanks for your help. You're certainly right about the duplicate
function...and of course I should have known that already.
But I'm a little confused about your statement that I shouldn't do this:
cfif NOT isDefined(mystruct)cfset this.init()/cfif
I could
Thanks again for the suggestions. Last question, I swear: why do you not like
using the cfscript tag at the top of your components? That seems to be the
cleanest solution, since you don't have to explicitly call the init function
outside of the component. Is there a performance hit to this
Thanks again for the suggestions. Last question, I swear:
why do you not like using the cfscript tag at the top of
your components? That seems to be the cleanest solution,
since you don't have to explicitly call the init function
outside of the component. Is there a performance hit to
If you do this:
cfset var s = structNew()
cfset s = mystruct
Then s is not a struct, but a pointer to mystruct, so
whenever you set a property of s, you are in fact setting a
property of mystruct.
There are two things worth pointing out here, I think. The first, trivial,
point is that
6 matches
Mail list logo
