Re: [Csnd-dev] break and continue
Steven Yi <[email protected]> Mon, 13 Oct 2025 13:45:57 -0400
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <CANtcCs68CxEAA0oO0sq9oAqbYqEeRNJVsmEE6YS1x4OFApT=LA@mail.gmail.com> |
+1 to implicit break. On Mon, Oct 13, 2025 at 7:56 AM Rory Walsh <[email protected]> wrote: > > +1 > > On Mon, 13 Oct 2025 at 12:54, Eduardo Moguillansky <[email protected]> wrote: >> >> Csound being mostly used by non-professional programmers, simplicity and terseness are probably more important than compliance. In that sense, an implicit break seems better: we spare the need of a break line for every case and also avoid unwanted fall-through mistakes. >> >> Eduardo >> >> >> On Mon, Oct 13, 2025 at 1:12 PM Victor Lazzarini <[email protected]> wrote: >>> >>> Hi all, >>> >>> with thanks to @scottsitar we now have break and continue in while, until, and >>> for loops. >>> >>> What we’d like to discuss here now is how switch should be handled. At the >>> moment, switch has an implicit break. This means it cannot be used in fall-through >>> scenarios (as far as I can see). Discussing briefly this in the PR we considered two >>> options: >>> >>> (a) modify switch to take an explicit break (like in C) >>> (b) add a fall-through statement (like in go) >>> >>> The advantage of (a) is that we don’t need a new keyword and we are in line with >>> the most common approach (?). The advantage of (b) is that no user-level changes >>> to switch are needed. >>> >>> I have no preference myself. Would be interesting to hear opinions. >>> >>> best >>> ======================== >>> Prof. Victor Lazzarini >>> Maynooth University >>> Ireland >>> >>> >>> >>> >>> >>>