Closed jerronjames closed 9 years ago
What is that crazy syntax?
log text="Event Gateway #variables.id# started" file=this.logfile;
Can you point me it's documentation.
found it: http://www.getrailo.org/index.cfm/whats-up/railo-40-released/features/tags-in-cfscript/
For a while now, Railo has had the ability to use most of the built-in tags within the <cfscript> tag.
All you have to do is remove the <cf at the start and usually, if it is a single line replace the > at
the end with ;....
How about tags that wrap some kind of content? Tags like <cfmail>, <cfloop> and <cfquery>?
They are just as easily used with {} brackets!
Maybe just me, but seems an arbitrary way to make the language more complex. What is wrong with functions?
Oh, I should point out. That code is actually in the railo code base, not ours. I just thought I’d document it.
From: ryaneberly [mailto:notifications@github.com] Sent: Friday, May 15, 2015 6:14 AM To: cflint/CFLint Cc: Jerron James Subject: Re: [CFLint] Misc. Parsing Error? (#54)
found it: http://www.getrailo.org/index.cfm/whats-up/railo-40-released/features/tags-in-cfscript/
For a while now, Railo has had the ability to use most of the built-in tags within the
All you have to do is remove the <cf at the start and usually, if it is a single line replace the > at
the end with ;....
How about tags that wrap some kind of content? Tags like
They are just as easily used with {} brackets!
Maybe just me, but seems an arbitrary way to make the language more complex. What is wrong with functions?
— Reply to this email directly or view it on GitHubhttps://github.com/cflint/CFLint/issues/54#issuecomment-102383827.
log is implemented, but there is a whole mess of tags to handle this way.
I'm wondering if there's a simple way to parse and flag them? Personally, I think they should be flagged critical to not use. However, the question remains... simple way to identify them?
the same logic was used to define the cfscript version of cfcomponent
identifying them should be relatively simple. There's just a lot of busy work putting the keywords into the lexer. .
On Fri, May 15, 2015 at 11:17 PM, jjames967 notifications@github.com wrote:
I'm wondering if there's a simple way to parse and flag them? Personally, I think they should be flagged critical to not use. However, the question remains... simple way to identify them?
— Reply to this email directly or view it on GitHub https://github.com/cflint/CFLint/issues/54#issuecomment-102567297.
fixed.
Misc Violation in CFLint-result:
Function being parsed: