Details
Assignee
UnassignedUnassignedReporter
Adam CameronAdam CameronLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Priority
New
Details
Details
Assignee
Unassigned
UnassignedReporter
Adam Cameron
Adam CameronLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Priority
Created 18 February 2015 at 05:09
Updated 11 July 2021 at 16:08
See equiv CF bug: https://bugbase.adobe.com/index.cfm?event=bug&id=3941602
SSIA, really.
This functionality is specifically related to CFCs, and only makes sense if implemented on a CFC-by CFC basis.
Indeed, the setting shouldn't be necessary at all! This should just work:
~~~~
// General.cfc
component {
property x;
function getX(){
return x;
}
function setX{
variables.x = arguments.x;
}
}
~~~~
~~~~
// general.cfm
o = new General();
o.x = "value"; // calls setX()
writeOutput("Value from o.x: #o.x#<br>"); // calls getX()
~~~~
It shouldn't need a setting for this to work. It should just work!
I was tempted to raise this as a bug because it's just a shoddy approach to the functionality, but I suspect you were just copying Adobe. So it's their fault