On 04/28/2012 07:54 AM, [email protected] wrote:
>> I apologise for my poor explanation. I further assure, the codes are not
>> magically created, they are created by the EBNF below. I regenerated the
>> EBNF to make me as clear as possible, in fact, now they are two:
>>
>> 1(0|1){1(0|1)}{0(0|1)}0(0|1)1(0|1)
>>
>> 1(0|1){0(0|1)}{1(0|1)}1(0|1)0(0|1)
>>
>>
These oft-repeated incomprehensible strings of symbols would be a whole
lot more intuitively understandable if, say, you were to use a
_different_ symbol for "either 0 or 1" and not "(0|1)" (and maybe some
spaces to split it up for the eye), and/or there were an actual
*explanation* of what they meant, as in:
1 X {1X}... {0X}... 0 X 1 X
1 X {0X}... {1X}... 1 X 0 X
and words like "... The bits in odd-numbered positions [counting from
zero] can be either value and hold the data being transferred; in the
even-numbered positions the first [zeroth] bit is 1, followed either by
a a string of 1s, then 0s, ending with 0 1; or else a string of 0s, then
1s, ending with 1 0." Or something like that, maybe done better. My eyes
glaze over at the sight of what looks like a random selection out of
[{}10|()]*, and I'm probably not the only one.
~mark
