Hello, Sean.
2012/8/2 Sean Bartell :
>> Now, concretely: in parse_if, you jump into a conditional block. I
>> would consider that a very bad practice and actually I am surprised
>> that such jump does not produce any warning. Better is to go with the
>> common practice and put the error block at t
Hello, Vojtech,
Vojtech Horky on 2012-08-01:
> > I implemented "if" today, but documentation, examples, and "switch" will
> > have to wait for tomorrow.
> The functionality side is okay. I played with it a bit and it works fine.
>
> However, you are still behind your (revised) schedule. And the a
Hello, Sean.
2012/7/30 Sean Bartell :
>> > However, many cases are not yet possible; for instance, USB descriptors
>> > can't use the length field because it includes its own length. This will
>> > be possible once scripts can get arbitrary subblobs.
>> I am not sure I follow. I thought that these
Hello, Vojtech,
Vojtech Horky on 2012-07-29:
> 2012/7/29 Sean Bartell :
> > I've finished implementing parameters in Bithenge. You can see the
> > possibilities in the new example file[0]. Parameters make it possible to
> Good job. I have tried it and it works :-). Though I was confused a
> bit wh
Hi Sean.
2012/7/29 Sean Bartell :
> Hello, everyone,
>
> I've finished implementing parameters in Bithenge. You can see the
> possibilities in the new example file[0]. Parameters make it possible to
Good job. I have tried it and it works :-). Though I was confused a
bit where the .len (in pascal_s
Hello, everyone,
I've finished implementing parameters in Bithenge. You can see the
possibilities in the new example file[0]. Parameters make it possible to
handle fields of known length as well as length fields followed by data.
However, many cases are not yet possible; for instance, USB descript
