Case Range Statement ..

[Leandro Lucarella]

Andrei Alexandrescu, el  7 de julio a las 10:19 me escribiste:
> Token meaning has ALWAYS depended on context. ALWAYS.

I can use the exact same argument for using case X..Y: then =)

At least let's agree one is as arbitrary as the other... I can live with
that syntax if you (people who likes case X: .. case Y: is better) accept
that is just a cosmetic issue and you like your syntax better (and since
who make the decisions likes it better, it will stay like that).

Can you at least use:
case X:
..
case Y:

in the examples/documentation/specs? I think most case X: .. case Y:
haters found that format pretty acceptable, so we can all be a little
happier =)

-- 
Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/
----------------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------------