tracker issue : CF-3863521

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Doc Bug for: cfdump() _is_ supported

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 12/07/2014

Components: Documentation

Versions: 11.0

Failure Type: Unspecified

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Trivial / Some users will encounter

Locale/System: ALL / Platforms All

Vote Count: 0

Currently, the cfscript doc says:

The script support is not available for the following tags:

<cfscript>
<cfoutput> (use writeOutput() instead)
<cfdump> (use writeDump() instead)
<cfinvoke> (use invoke() instead)
<cfinvokeargument>
<cfobject> (use createObject instead)

However, <cfdump> should be removed from that list b/c it is supported in CF11 Final (11,0,0,289822).  Repro:

index.cfm
---------
<cfscript>
  cfdump(var={foo=["bar"]});
</cfscript>

Dumps {foo=["bar"]}

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3863521

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Related URL: https://wikidocs.adobe.com/wiki/display/coldfusionen/cfscript#cfscript-Scriptsupportfortags
Comment by External U.
9645 | December 07, 2014 04:25:43 PM GMT
I've updated the doc. This ticket can be marked Closed/Fixed. Thanks!, -Aaron
Comment by External U.
9646 | December 07, 2014 04:30:34 PM GMT
@Aaron, though it works because of the generic implementation, we don't want to support it. We clearly want you to use writeOutput instead of cfoutput(), writeDump instead of cfdump(), invoke() instead of cfinvoke() and cfinvokeargument(), createObject() instead of cfobject(). We are going to put it back in the documentation with a note saying the above.
Comment by Rupesh K.
9647 | December 08, 2014 05:57:34 AM GMT
I think it's foolhardy to have "generic syntax" and then not support some of it. That breaks the predictability of the language. If anything, you should run with the generic version and deprecate the non-generic.
Comment by External U.
9648 | December 10, 2014 03:32:44 AM GMT
And there's no reason to *not* support it. It's just a wrapper for writeDump(), I hope? Or both are wrappers for the underlying <cfdump> code or something? Not two separate pieces of code.
Comment by External U.
9649 | December 10, 2014 03:33:25 AM GMT
Hi Adam, I agree. Imaging teaching someone CF now: "Look, student, the CF language is very predicable. There is a function w/ the same name for each tag. The tags, and their same-named functions, take the same arguments. Oh, but wait, there's 5 "special tags and functions" that you need to remember are different: <cfdump> is writeDump(), <cfobject> is createObject(), <cfinvoke> is just invoke(), etc, etc. :/ Why must we continue having these quirks in the language? Thanks!, -Aaron
Comment by External U.
9650 | December 10, 2014 04:19:53 AM GMT
"Imaging" should've been Imagine
Comment by External U.
9651 | December 10, 2014 04:21:26 AM GMT
Because it's a way for the ColdFusion Team to do less work. That is the only rationale I can come up with for this. It's definitely not "planning" or "design" or "the best for the language".
Comment by External U.
9652 | December 10, 2014 04:21:58 AM GMT