@seancorfield wrote:
I think there's a fundamental philosophical decision that LAS need to make about Lucee:
Is Lucee meant to be a language that enshrines best practices to appeal to a broader range of developers (i.e., outside the CFML pool), or is it meant to be "just CFML.Next" and carry over the sort of "quick'n'dirty" solutions that have given CFML such a bad reputation amongst so many non-CFML developers?
Many language design decisions cannot be made in a vacuum of just syntax and semantics. They need to be informed by the vision and mindset of the language philosophy. I think this is exactly one of those issues.
The "best practices" answer says: each tag should do one thing and do it well -- don't mix in unrelated functionality.
The "quick'n'dirty" answer says: sure, add
exit="true"-- but add it to every tag that could conceivably need to be the last executed one in a file.