-
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
"if" without an "else" triggers "Nothing to parse" warning #222
Comments
denuno
added a commit
that referenced
this issue
Dec 7, 2016
@mpaluchowski , Thanks. I cannot duplicate this issue with the latest code, but I don't think the PARSE_NOTHING is a useful warning regardless. I disabled it (dev branch) |
Got it. Thanks!
…On Sat, Dec 10, 2016 at 3:21 AM, Michał Paluchowski < ***@***.***> wrote:
@denuno <https://github.com/denuno>'s a303ef4
<a303ef4>
commit to dev seems to have fixed it. I was just waiting for it to merge
to main.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#222 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFtZu7LWjTZXdeksIsQiC4Te_vo5m0jtks5rGmEYgaJpZM4LFXu2>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code will cause CFLint to produce a "Nothing to parse" warning:
while the following code will not:
The warnings multiply, so if a component has 5 instances of an
if
clause without anelse
, it'll trigger 5 "Nothing to parse" warnings.The text was updated successfully, but these errors were encountered: