/ ,

I’ve added a pull request to the Lucee docs:

I agree with the doc updates suggested above. You can send a pull directly to the Lucee docs and CFDocs.org, both of which use markdown or JSON on github.

https://github.com/lucee/lucee-docs/edit/master/docs/03.reference/01.functions/isnull/function.md

https://github.com/foundeo/cfdocs/edit/master/data/en/isnull.json

Just a note- before Lucee makes any decision on this ticket, it’s worth noting Adobe did mark their ticket “to fix” which would seem to imply they are willing to change their behavior to match Lucee’s. Of course, it remains to be seen if Adobe will actually ever do anything, or when they do, if they’ll do it correctly

If this existing behavior is deemed to be correct, I would recommend at least updating the docs for the isNull() function ( ) so they mention that to explicit check for null values in a UDF that you should scope the variable. Perhaps something like:

Determines whether given object is null or not.

When testing the presence of null values unscoped variables will use scope precedence to determine if the variable exists in any scope. This behavior differs from Adobe ColdFusion. So when testing when local variables in a function are null, it’s important to prefix the variable with the local scope.

For example, in the following code the variable name would return false for the isNull() if name ends up in a user supplied scope, such as the URL or FORM scopes:

In order to make sure that only the local name variable is checked, you would change the code to:

Lucee’s behavior is correct and Adobe’s is incorrect. Given CFML’s rules, null values do not exist. Therefore, if you were to dump out modelID, you would correctly scope-hunt up to the url scope where the variable would be resolved, therefore not being null. If you want null to be an acceptable value for a variable, then enabling full null support in Lucee will cause the code to work in the manner you want. Otherwise, just scoping your variable so it’s clear what you’re checking for null-ness will also work.

To summarize:

• Given the rules of CFML echo( modelId ) returns a value because modelID is resolved to a found, non-null value

• Therefore, isNull( modelID ) is correct to return false as the echo above clearly shows modelID not null.

• If you want to explicitly check if local.modelID is null, then use the code isNull( local.modelID )

I have entered this ticket for Adobe’s incorrect behavior:

Which can be seen in this Gist:

Is there any update on this issue? I keep running into issues due to this behavior.