Copied from https://issues.jboss.org/browse/RAILO-1510
had added a comment:
I don't know how much work adding this option would be so I'll leave the decision up to Micha but I wanted to point out that Adobe ColdFusion Builder does a great job of highlighting syntax that won't work on Adobe ColdFusion. I use CFBuilder for all my Railo development and it really helps me keep my code portable (in terms of syntax - Railo supports a lot more tags in cfscript, optional semicolons and the ability to dynamically call methods in cfscript: obj[method](args) - which is a syntax error on ACF; CFBuilder highlights all of those).
Looking at this in preparation for TAG meeting 16/09/15.
Given the idea of moving Lucee into a situation with an ACF-compatible CFML language as well as LuceeLang for new features that can part with ACF-compatibility, wouldn't this be best solved by going forward making it required (as ACF does) in LuceeCFML and make them optional in LuceeLang?
TAG recommends admin configuration. Classic vs modern for example. Setting also available via Application.cfc.
Fixing status based on new workflow. Rejecting just to get it to "start over".
[ 5 votes ] Reject
[ 3 votes ] Add to backlog
Reasons for rejection
Portability checking is the remit of a separate tool such as ColdFusion Builder
Unless Lucee decides to add a full strict ACF compatibility mode there is not much point in addressing the issues piecemeal
If Adobe wish to support all CFML that Lucee does they are welcome to do so, it is up to Lucee to ensure code that works on ACF also works on Lucee and not the other way around.