tracker issue : CF-4202429

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

Null cannot be used as a component name

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Tom King / ()

Created: 05/14/2018

Components: Language, Null Support

Versions: 2018

Failure Type: Others

Found In Build/Fixed In Build: Beta / 2018,0,0,309454

Priority/Frequency: Normal /

Locale/System: / Windows 10

Vote Count: 0

Problem Description:
Null cannot be used as a component name

Steps to Reproduce:

<cfscript>
foo = new Null()//coldfusion.runtime.UndefinedVariableException
writeDump(foo)
</cfscript>

Actual Result:
Variable undefined exception

Expected Result:
Component

Any Workarounds:

Attachments:

Comments:

Hi Adobe, Original ticket in PR: CF-4201487 <cfscript> function f(null=true) {//coldfusion.compiler.ParseException writeDump(null); } f(); </cfscript> <cfscript> foo = new Null()//coldfusion.runtime.UndefinedVariableException writeDump(foo) </cfscript> Re-open/fix/communicate. Thanks!, -Aaron
Comment by Aaron N.
27802 | May 14, 2018 11:27:46 PM GMT
The only scenario that has not been fixed as part of CF-4201487, is,  <cfscript> foo = new Null()//coldfusion.runtime.UndefinedVariableException writeDump(foo) </cfscript> In fact, the following snippet works as expected, <cfscript> foo = createObject("component", "Null"); writeOutput(foo.get()); </cfscript> Will be looking into this issue as part of this bug.  Updated the description accordingly. 
Comment by Immanuel N.
27817 | May 15, 2018 01:28:30 PM GMT
Hi Immanuel, Thanks very much for confirming. I did report on Apr 30 that the `foo = new Null()` still wasn't fixed, but no replies. That PR tracker is a bit of a black hole when it comes to communication :) Thanks!, -Aaron
Comment by Aaron N.
27821 | May 15, 2018 09:34:50 PM GMT
new Null() is now fixed, Aaron.  Will be available in the next build. 
Comment by Immanuel N.
27827 | May 16, 2018 05:29:40 PM GMT