@modius wrote:
Hmm.. interesting. Never knew you could do
<cfdump abort="true">
(since CF9 to boot).<cfdump var = "#variable#" output = "browser|console|file" format = "text|html" abort = "true|false" label = "text" metainfo = "yes|no" top = "number of rows|number of levels" show = "columns|keys" hide = "columns|keys" keys = "number of keys to display for structures" expand = "yes|no" showUDFs = "yes|no">
I can see that it would be useful in code bases where a lot of code is broken out with includes.
In a practical sense it seems easier to "cut and paste" or "hot key" in a cfabort beneath a cfinclude than to change the abort attribute. And I can't think of a scenario where I'd be populating the abort attribute with a variable.
While I'd argue that its appropriate in cfdump as its a tool for debugging, I'm not convinced its appropriate in cfinclude.