I'd forgotten about structCopy(). Wasn't the whole point of duplicate() to replace
structCopy() because structCopy doesn't do a deep copy? So now it's the other way
around? I'll try it...
Yep, it works (at least in this case)! Thanks!
>>This bug is killing me. I have a collection class for
>This bug is killing me. I have a collection class for my companies plants.
> It creates a structure, the key of which is the plant number, and the
>value is the plant object for that particular plant. One of the methods is
>getPlantByNumber('01'), and it works fine- you pass the plant number
This bug is killing me. I have a collection class for my companies plants. It
creates a structure, the key of which is the plant number, and the value is the plant
object for that particular plant. One of the methods is getPlantByNumber('01'), and
it works fine- you pass the plant number in a
Yes, this is a known bug. I don't recall the bug number. It's been
talked about for quite some time. However, if you look at how classes /
objects behave in Java and other languages, you wouldn't normally
expect a simple 'duplicate' function to do the right thing... that's
why you need to expli
When you duplicate an object it is converted from an object to a struct, and
any private variables the object had are lost. The following code
demonstrates the bug:
oServer = createObject("component","wgc.common.serverObject");
When b is dumped, the object is shown to be no longe
5 matches
Mail list logo
