Any reason this isn't just a bug: https://trycf.com/gist/2ac785b4f22ac3920e4f5a0958e8b32c/lucee5?theme=monokai

cfhttp(url="<https://example.com>", result="responseFromExample")
writeDump(responseFromExample.statusCode)

CF:

200 OK

Lucee:

variable [RESPONSEFROMEXAMPLE] doesn't exist on line cfhttp(url="https

I suspect this is a case that Lucee is getting confused because there's a possibility that there is more to the

cfhttp

"tag" than just the initial statement... it could optionally have a following block. CF gets it right: the next token after the initial

cfhttp

is not a

{

, therefore that musta been the end of the statement, and the next token is the beginning of a new statement. Lucee should also be able to do this. Yes?

OMG someone please check on Adam, I think he may have been kidnapped!

CF gets it right

HA

I agree. I think Lucee is trying too hard to see if there's more to the cfhttp(), but when using the ACF syntax with the parens, it should be pretty easy for Lucee to tell even without a semi-colon when it's done.

Correct.