OK, so I guess native lucee cftag syntax is no parens, args with equal signs:
tagname_without_cf_prefix arg="val" arg2="val" {
// optional body
};
Now what about custom tags though? Our project has a bunch of them but they don’t seem to follow the same rules… I left this out of the initial report, but maybe related?
<!--- custom logging tag --->
<cf_tag_trace outputline="some debugging output">
<cfscript>
cf_tag_trace(outputline="got here"); // works
cf_tag_trace(outputline: "got here"); // works
cf_tag_trace outputline="got here"; // Error: Missing [;] or [line feed] after expression
tag_trace outputline="got here"; // Error: Missing [;] or [line feed] after expression
tag_trace(outputline="got here"); // Error: No matching function [tag_trace] found
// positional args? nope :(
cf_tag_trace("got here"); // Invalid Identifier, the following character cannot be part of an identifier ["]
</cfscript>