tracker issue : CF-3174462

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

Custom functions named "trace" don't raise the expected errors

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Sam Dealey / Sam Dealey (isaac dealey)

Created: 04/24/2012

Components: Language

Versions: 9.0.1

Failure Type: QA Work Item

Found In Build/Fixed In Build: 9.0.1 /

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Win 2003 Server

Vote Count: 0

Problem Description: Normally when a new function is added, the server produces an error when it encounters a custom function with a matching name. This doesn't occur with the new Trace() function - custom functions are compiled and then produce confusion later when attempts to call them call the native function instead. Also the trace function isn't included in the list of errors reported by the CF9 code analyzer in the CFIDE. 

Steps to Reproduce: <cffunction name="trace" access="public" output="false"><cfreturn "hello world" /></cftrace>
<cfoutput>#trace()#</cfoutput>

Actual Result: An error regarding the first argument of the native trace function occurring on the cfoutput line. 

Expected Result: An error stating that "trace" is the name of a native function and the custom function must be renamed. 

Any Workarounds:

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

Watson Bug ID:	3174462

External Customer Info:
External Company:  
External Customer Name: isaac dealey
External Customer Email:  
External Test Config: My Hardware and Environment details: I don't think they matter in this case, but I'm using 32-bit Windows 2003 Server.

Attachments:

Comments:

I expect it may not be fixed this late after the release of CF9, but it might be fixed for the CF10 release.
Comment by External U.
19683 | April 24, 2012 09:15:26 PM GMT
I see that you have used </cftrace> instead of </cffunction>. Can you try this on CF 10 public beta and see if it still throws an error? (Comment added from ex-user id:sagarg)
Comment by Adobe D.
19684 | April 25, 2012 11:06:21 PM GMT
Checked the code on the latest build of CF10 & 11. It throws the error as expected. So closing the bug as cannot reproduce
Comment by Suchika S.
19685 | December 03, 2014 03:51:16 AM GMT