Q: Do you use the Lucee syntax to get things done or do you play it safe?

'lucee syntax'?

like looping over a query in cfscript syntax.

pretty sure you've been able to do that in acf for a while now

I'm guessing you're referring to the Lucee language syntax that was introduced but I think has been deprecated.

yeah there used to be things like

object[method]()

that you could only do on Lucee but I think ACF has most of them now

Does acf use

loop query=q {}

don't think I've ever seen anybody use that. we would just do:

for ( var row in query ) {}

queryEach(), queryFilter(), queryMap(), etc.

And I've never used those 3 functions. Yikes.

I haven't either, but only because I prefer treating queries as arrays of structs rather than the CF 'query object'

You can use the equivalent version of those for arrays.

Ugh. Come on. Stop trying to be clever and demonstrate you know things that might've been incompats in Lucee at some point, but aren't now. Well done: you've clever. There are still things in Lucee that are not compatible with ColdFusion, and that's what @phillipsenn is talking about. It was a simple question. To give a useful answer (maybe): we use whatever syntax is most expedient in Lucee, and don't care if it works in CF. We are, however, in a situation where we 100% know that this software will never need to be run on CF: it is being decommissioned (albeit slowly), and will be shifted off CFML altogether before it would ever shift to CF (no slight on CF... just that it's on Lucee now, and on Lucee it will stay). For my own code... I would not actively use functionality that is Lucee-specific, no. I think it was a mistake on Lucee's part to ever develop features that are not part of CF.

There are still things in Lucee that are not compatible with ColdFusion,

like such as? perhaps you have a list that isn't deprecated? I don't, I'm not clever

[1,2,3].each() but that's more a bug in ACF I would say.

while it may be obvious to (some people, e.g. Adam), it's not obvious to me what 'lucee syntax' meant, so while it may be a simple question, it isn't an unambiguous question, and in my experience many of the old incompatibilities are no longer incompatible this in no way rules out the existence of current incompatibilities, but it sounds like the question was about a specific type of expression, and so it seems relevant whether the question relates to "functionality intentionally specific to Lucee" (which I agree was generally a bad idea) versus "functionality Lucee happened to get to first which ACF added later" aside from that, it's in no way appropriate to go picking a fight over an otherwise banal question, so perhaps Adam will consider exchanging what might charitably be interpreted as a 'shut up, other people' for his customary direct answers that we all know and love

There are also some behaviours in lucee which are different to defaults in ACF eg arrays pass by reference but I know you can set a config setting in acf to do that. In terms of BIFs you might find some new ones. I personally don’t see it as an issue that lucee deviates and or adds new features as really only framework developers are bouncing between engines.

echo()?