bug is a word that you use at your own risk around here.
a "caseless" case will not compile in a switch block in java.
so the ability to handle a "caseless" case in b4x was a deliberate
decision. one could argue that it might better be handled differently.
run the routine as normal and look at the resultant java code.
then remove the "," after "case" and run again.
look at the resultant java code.
you'll see that an empty case does 2 things: it generates a default action
(aka, "case else"), the other cases are simply ignored and construction of
the switch block in java aborts.
when you remove the empty case, the resultant java code behaves as
expected.
as for me, i would prefer a warning (at least) for the empty
case. i would also like to see a warning for a missing "case else".
(without it, the programmer and the user see nothing if none of the
available cases is matched. not particularly helpful.)
a "caseless" case makes no sense. (note: an empty string - "" - is not a
caseless case.) exceptions are often generated for errant or missing punctuation.
turning a caseless case into the default behavior may not be what anybody wants.
and case else serves an important purpose. its absence should prompt some comment
from the compiler.