fall through _is_ the default in C, which can be a very annoying characteristic.
I would leave out fallthrough entirely. Not worth the effort, mostly theoretical cases only.
I disagree here. We used to use that a lot in C libraries where some of the options needed preparatory setup before any option later in the switch could be executed, example: partial information need to be completed first. E.g. when a ticker was not yet in the cache, so its static information needed to be retrieved first before processing trade information.
I seem to remember I once suggested to use continue for that, so you get basically kind of a reverse syntax to C, but introducing at least the option to fall-through.
It was refused, not only as a feature, but also because it was not needed if the case labels would allow overlap anyway, shame on me
. (I was thinking about re-labeling, or case labels as true sets)
I still think that the mutual exclusiveness for case labels is a limitation rather than a feature.
Although similar solutions can be written such a feature is not only notational candy, but a clear grouping of related code. It enhances readability. {$modeswitch OverlappedCaseLabels}?