Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add another sequential list example to stage_1 #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add another sequential list example to stage_1 #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions stage_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,16 @@ false && echo foo || echo bar
true || echo foo && echo bar
```

This should echo "foobar":
```
true && printf foo || false && printf bar
```

This is equivalent to:
```
(((true && printf foo) || false) && printf bar)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, but we don't want to give misleading syntax around () (which are not grouping, but subshell, in sh); maybe we can be explicit about the associativity in another way?

I would suggest { { { true && printf foo; } || false; } && printf bar; } but this is probably even less clear.

Thanks!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is a good point. Thinking about it more, maybe the best way is to use parens but also explicitly state that they're meant to indicate associativity, not subshells?

Either that or just remove the attempt to show the associativity, and just use this as an example.

```

The standard calls these *sequential lists*, *AND lists*, and *OR
lists*, respectively. See section 2.9.3, [Lists]. We'll look at
*asynchronous lists* in stage 3.
Expand Down