-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MISSING_SEMI false positive in if/else #289
Comments
Trying to ignore the MISSING_SEMI here leads to the same issue as reported in #285. I've tried to put // cflint ignore:MISSING_SEMI on lines 8 and 10 to the right of the code - doesn't do anything. Tried to put it above each of the offending/reported lines - doesn't do anything either. |
Interesting enough, putting
above the |
Ahh, actually the same file triggers this, too:
which now makes me think that the core of this whole issue might be that CFLint thinks myFusebox.do("k.l"); is actually starting a do-while loop? |
created this issue in the cfparser project |
@TheRealAgentK . Yes, you are correct. Do is a reserved word. I am changing the parser to be aware of the differences between a member function call and an unqualified function call. You could work around it today if you are able to rename your do() function. |
fixed in cfparser 2.4.6 |
Wow, you've been on a roll! :) Will give all of your fixes and changes a good test against my offending code during the weekend. Does cfparser get pulled into the cflint maven build automatically? |
Thanks. No, to get the parser fixes: or wait a week on those few, I'll push cfparser out to maven soon. |
I just built it locally and it seems to run fine with my local cfparser 2.4.6 I do get a message about ANTLR 4.6 vs 4.7 though when running cflint. ... Have updated all references in the pom to Antlr 4.7 though. |
The MISSING_SEMI issue is actually working fine now with that myFusebox.do(), too :) |
Result:
The offending lines are:
else if (structKeyExists(variables,'g') && variables.g) {
and
myFusebox.do("k.l");
The text was updated successfully, but these errors were encountered: