Re: 255UInt16 spec

+1 for this being hard to follow.

I would find pseudo-code (bonus points for giving actual code :D) much
easier to follow than that table.



On Sat, Mar 28, 2015 at 1:03 PM, Khaled Hosny <khaledhosny@eglug.org> wrote:

> On Sat, Mar 28, 2015 at 02:55:46PM -0400, Behdad Esfahbod wrote:
> > IMO this is a very clumsy description of the encoding.  What do "Data
> Type"
> > and "Syntax" columns mean in this context?!  I understand the encoding
> from
> > putting everything together, but think the table should be rewritten.
>
> Same here. I couldn’t make much sense of this table and ended up just
> checking the reference implementation.
>
> Regards,
> Khaled
>
>