Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

non-typesafe compare with null throws ExpressionException

Description

Having null support enabled, comparing a complex value against null throws an ExpressionException when using the non-typesafe operator ==. Using the typesafe operator === works as there is no attempt to cast the complex value.

 

s = {}; structIsNull = (s == null); // throws ExpressionException: Can't cast Complex Object Type Struct to String structIsNull = (s === null); // works

 

This is an unexpected behavior and casting to String seems to indicate an improper fallback.

I would have expected it to work like Javascript:

This bug is possible related to https://luceeserver.atlassian.net/browse/LDEV-2498#icft=LDEV-2498.

Environment

// Application.cfc this.enableNullSupport = true;

Attachments

1
  • 25 Nov 2019, 09:19 pm

Activity

Show:

Michael Offner 20 December 2019 at 15:41

CFML does not support comparsion of complex objects (struct, array,…), why acf does allow this in that case but not others makes no sense. i will do some more testing on this.

Pothys - MitrahSoft 26 November 2019 at 08:10

I've checked this ticket & confirmed the issue happened on lucee latest version 5.3.5.42-SNAPSHOT. If we check as per ACF means, structIsNull = (s == null); lucee throws an error for this. But, ACF works fine. If we use serialize(struct), it will works fine.

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 25 November 2019 at 21:21
Updated 19 May 2021 at 11:55