This is a bit related to this issue:
http://code.google.com/p/bitstring/issues/detail?id=13
Since one cannot put a bitmatch after a semicolon, we might want to try "... ;
begin bitmatch ... end" instead. However, this isn't accepted either:
Parse error: "end" or [sequence] expected after "begin" (in [expr])
So, the only true solution at the moment is to enclose every bitmatch within
parentheses. This works well, but some people prefer begin-end-delimited blocks.
Original issue reported on code.google.com by valentin.robert.42 on 3 Apr 2012 at 2:20
Original issue reported on code.google.com by
valentin.robert.42
on 3 Apr 2012 at 2:20