We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had to write this because of very long case/break , for using folding functions of my editor (kde4 enviro):
switch (variable) { case condition1 : { [... 412 lines] } break;
case condition2 : { [... 96 lines] } break;
}
this lead to :
Line ### : { Expected to see a statement and instead saw a block.
The text was updated successfully, but these errors were encountered:
What do { ... } accomplish in your examples? As I can see it could as well be:
switch (variable) { case cond: [ 412 lines ] [ ... ] }
I don't see any disadvantages from using blocks here but I also don't see any advantages and I need to prioritize tickets.
Sorry, something went wrong.
I use kate (kde4 editor) and it helps it to see blocks. There is also the case when I disable temporary a condition.
By example
// if (!stabe_condition) { [ 412 lines ] }
This is not bogus, and you don't need to comment the brackets only for that.
Filter out acorn.parse_dammit placeholders from context-aware guessed…
15ec3a1
… completions Closes jshint#50
No branches or pull requests
I had to write this because of very long case/break , for using folding functions of my editor (kde4 enviro):
switch (variable)
{
case condition1 :
{
[... 412 lines]
}
break;
}
this lead to :
Line ### : {
Expected to see a statement and instead saw a block.
The text was updated successfully, but these errors were encountered: