Status/Resolution/Reason: To Fix/Deferred/EnhancementRequired
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 12/15/2014
Components: Language
Versions: 11.0
Failure Type: Usability Issue
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Normal / Most users will encounter
Locale/System: ALL / Platforms All
Vote Count: 20
This is appallingly awful syntax:
cfwddx(action="cfml2wddx", input={}, output="w");
a) It looks like a function, but isn't a function (although it SHOULD be a function!)
b) and it returns a value but one needs to pass the name of a variable INTO the construct.
This is ludicrous. Ludicrous.
Functionality like this should have been implemented like this:
w = wddx({}, "cfml2wddx"); // although for non-WDDX input in the first argument, the action can be inferred.
Or perhaps:
w = cfmlToWddx(/* etc */);
Or *better*, have a .toWddx() method on the various CFML data types. THAT would be a good solution. You should aim for good solutions, not ratshit lazy ones like you've given us in CF11.
And I don't just mean cfwddx()... I mean ALL of the previously tag-only functionality needs to be revisited. You need to do your jobs like professionals. Your clients rely on this. And pay for this.
--
Adam
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3909712
External Customer Info:
External Company:
External Customer Name: Adam Cameron.
External Customer Email:
External Test Config: My Hardware and Environment details:
Attachments:
Comments: