tracker issue : CF-4199819

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

Null can't be used as functionName

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron ()

Created: 09/26/2017

Components: Language, Null Support

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: / 305171

Priority/Frequency: Major / Some users will encounter

Locale/System: /

Vote Count: 0

Problem: Null keyword can't be used as function Name inside CFscript.

Method:The following piece of snippet should work for backward compatibility

{code:java}
<cfscript>
function null( param1, param2 ){
  var x = arguments.param1;
  var y = arguments.param2;
  return x+y;
}
WriteOutput(null(1,4));
</cfscript>
{code}


Result:
"Error","http-nio-8500-exec-1","09/13/17","01:21:58","","Invalid CFML construct found on line 2 at column 1.ColdFusion was looking at the following text:<p>function</p><p>The CFML compiler was processing:<ul><li>A cfscript tag beginning on line 1, column 2.</ul> The specific sequence of files included or processed is: P:\cfusion\wwwroot\CF-4199054\test.cfm, line: 2 "
coldfusion.compiler.ParseException: Invalid CFML construct found on line 2 at column 1.
	at coldfusion.compiler.cfml40.generateParseException(cfml40.java:14408)
	at coldfusion.compiler.cfml40.jj_consume_token(cfml40.java:14279)
	at coldfusion.compiler.cfml40.cfscript(cfml40.java:1632)
	at coldfusion.compiler.cfml40.cfml(cfml40.java:4917)
	at coldfusion.compiler.cfml40.start(cfml40.java:5353)
	at coldfusion.compiler.NeoTranslator.parsePage(NeoTranslator.java:655)
	at coldfusion.compiler.NeoTranslator.parsePage(NeoTranslator.java:635)
	at coldfusion.compiler.NeoTranslator.parseAndTransform(NeoTranslator.java:457)
	at coldfusion.compiler.NeoTranslator.translateJava(NeoTranslator.java:407)
	at coldfusion.compiler.NeoTranslator.translateJava(NeoTranslator.java:160)
Expected: 5

Workaround:

Note:

Attachments:

Comments:

This is fixed now.
Comment by Nitin K.
304 | December 10, 2017 09:58:01 AM GMT