Details
Assignee
Michael OffnerMichael OffnerReporter
Adam CameronAdam CameronPriority
NewLabels
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
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Adam Cameron
Adam CameronPriority
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
Created 14 May 2022 at 21:20
Updated 30 April 2024 at 15:35
I could not find an existing ticket for this case. Apologies if it’s a duplicate
Repro:
Result:
Expected:
Not an error. It is not a syntax error.
Work-around:
Put a semi-colon in.
Compat:
This works fine on CF2021.
Observations:
This is not really an edge case of the “semi-colons are optional” functionality in Lucee. I think it might be an idea to look at your testing for this lot, is it might require a bit more attention.
(thanks to for this one). Obvs(?) this is not something to fix just for this one example; the remit here is to fix the broader situation. I suspect you have an issue with how you are determining when the end of a statement is with that
cfwhatevertag
implementation. Maybe just when it’s one that can take an optional block? Dunno. But like…. as per my testing observation above… I don’t think this might benefit from a step back and identifying all the language constructs in CFML and what constitutes the end of those kind of statements. Then right tests for all of those. THEN get an idea of the scope of what needs fixing, and then start thinking about implementation code. Do not start by implementing a fix. Start with the tests. Starting with the implementation code and not the tests as perhaps caused this situation in the first place? Maybe. Anyway, you get the picture. Cheers.