Status/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 07/15/2012
Versions: 10.0
Failure Type:
Found In Build/Fixed In Build: Final / 283808
Priority/Frequency: Minor / Some users will encounter
Locale/System: English / Win All
Vote Count: 1
Problem Description:
The inner workings of <cfdump> bleed one of its "working" variables back into the calling code
Steps to Reproduce:
<cfdump var="#request#">
Actual Result:
One sees cfdumpinited FALSE in the output.
Expected Result:
It's nothing to do with my calling code, so it should not be bleeding into my request scope
Any Workarounds:
[just ignore it]
This is not so much of a problem as just being indicative of sloppy code. Fair enough for you to stick something into the request scope whilst <cfdump> is working as it's being called recursively, I get that. But if the code was well-polished, it'd tidy up after itself before exiting. I believe CF's inner workings should be more polished that this bleeding variable indicates.
I'm not saying this is a major issue, but it's also low-hanging fruit, so you should sort it out.
Cheers.
--
Adam
PS: I've had to tag this as CF10 because your bug tracker won't allow me to tag multiple versions. However it is relevant to previous versions of CF too.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3288046
External Customer Info:
External Company:
External Customer Name: Adam Cameron.
External Customer Email:
External Test Config: My Hardware and Environment details:
Attachments:
Comments: