ColdFusion Encapsulation Gotcha
Good object design dictates that we encapsulate our objects, hiding direct access to object properties from outside code. Access to the values of these properties is often granted to outside code with the use of ‘getter’ methods.
The following, useless, component appears to encapsulate its ‘foo’ property using a getter method but, as we shall see shortly, does nothing of the kind:
Why is that not encapsulated?
The reason the ‘foo’ property is not encapsulated here is that ColdFusion passes certain variable types by reference rather than value. So when we return the variables.foo structure we are actually returning a reference to the original data in memory rather than the data itself.
The following code demonstrates what effect this has:
If the ‘foo’ property were properly encapsulated here, both dumps would show the same thing. However, because we have a reference to the original data in the variables ‘fooReference’, we can make changes to the data directly (breaking encapsulation).
What to do about it?
It is important to note here that passing variables by reference saves memory - it is certainly NOT a bad thing! However, if encapsulation is more important to you, you can use the Duplicate() method to return a reference to a copy of the data which has the effect of returning the data itself:
ColdFusion passes queries, structures and external objects such as COM objects and CFC instances by reference.
Strings (including numeric values) and arrays are passed by value and do not need to be ‘duplicated’ in this way.
Here is a link to an Adobe livedocs page that talks about passing variables to and from functions in detail: