lezer/website
1
0
Fork 0
Code Issues Pull requests Activity

fix dangling else example #18

Closed
zhuscat wants to merge 1 commit from patch-1 into master
pull from: patch-1
merge into: lezer:master
Conversation 3 Commits 1 Files changed 1 +1 -1
zhuscat commented 2024-01-31 18:00:55 +01:00 (Migrated from github.com)
Copy link
No description provided.
marijnh commented 2024-01-31 18:07:00 +01:00 (Migrated from github.com)
Copy link

That breaks the example—with that change, the association of the else is no longer ambiguous.

That breaks the example—with that change, the association of the `else` is no longer ambiguous.
zhuscat commented 2024-02-02 04:49:21 +01:00 (Migrated from github.com)
Copy link

Thank you for your reply, but I'm still a little confused.

According to Dangling else, if we don't specify the precedence of else, the following code:

if (a)
if (b) {}
else {}

can be interpreted as:

if (a) {
  if (b) {}
} else {}

or

if (a) {
  if (b) {}
  else {}
}

But why is the following code ambiguous?

if (a) {}
if (b) {}
else {}
Thank you for your reply, but I'm still a little confused. According to [Dangling else](https://en.wikipedia.org/wiki/Dangling_else), if we don't specify the precedence of else, the following code: ```js if (a) if (b) {} else {} ``` can be interpreted as: ```js if (a) { if (b) {} } else {} ``` or ```js if (a) { if (b) {} else {} } ``` But why is the following code ambiguous? ```js if (a) {} if (b) {} else {} ```
marijnh commented 2024-02-02 09:50:23 +01:00 (Migrated from github.com)
Copy link

But why is the following code ambiguous?

It's not. And as such it's no use for illustrating this potential ambiguity.

> But why is the following code ambiguous? It's not. And as such it's no use for illustrating this potential ambiguity.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lezer/website!18
No description provided.