Timeline for Possible to match multiple conditions in one case statement?
Current License: CC BY-SA 4.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 15, 2020 at 22:27 | answer | added | jrw32982 | timeline score: 3 | |
Apr 4, 2020 at 6:22 | answer | added | user232326 | timeline score: 1 | |
Apr 3, 2020 at 8:41 | history | became hot network question | |||
Apr 3, 2020 at 4:52 | history | edited | MountainX | CC BY-SA 4.0 |
added 214 characters in body
|
Apr 3, 2020 at 4:49 | comment | added | MountainX |
@user1794469 - in this specific code I prefer the syntactic sugar of case statements. ;;& is the perfect solution here.
|
|
Apr 3, 2020 at 4:46 | vote | accept | MountainX | ||
Apr 3, 2020 at 1:42 | comment | added | steeldriver |
@user1794469 ah yes that would be the behavior with ;& I think
|
|
Apr 3, 2020 at 1:31 | comment | added | user1794469 | @steeldriver it totally is. I wasn't aware that's how that worked in bash. Fall through generally works by simply going to the next statement, not but testing the nest case, in other languages anyway. | |
Apr 3, 2020 at 1:08 | answer | added | steeldriver | timeline score: 125 | |
Apr 3, 2020 at 0:50 | comment | added | steeldriver |
@user1794469 isn't that exactly what ;;& does?
|
|
Apr 3, 2020 at 0:48 | comment | added | user1794469 | @steeldriver op doesn't seem to want fall through but rather multiple match | |
Apr 3, 2020 at 0:47 | comment | added | user1794469 |
Why not just use a series of if s that's basically all a case statement is, just syntactic sugar to make a bunch of if or ifelse look nicer.
|
|
Apr 3, 2020 at 0:46 | comment | added | steeldriver | Does this help? Can bash case statements cascade? | |
Apr 3, 2020 at 0:37 | history | asked | MountainX | CC BY-SA 4.0 |