You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Showing all the bounds components the capability encoding overview diagram immediately exposes readers to a lot of complexity that only needs to be understood when implementing the encoding/decoding. Grouping everything together as a BOUNDS field and having the bounds decoding section describe how this is interpreted would push some of that complexity to a more appropriate subsection.
I think the suggestions from @Timmmm in #23 (comment) makes a lot of sense:
The other thing that I think would make things clearer is a separate diagram for E=0, but that can probably wait, or maybe go in a separate explanatory document.
Showing all the bounds components the capability encoding overview diagram immediately exposes readers to a lot of complexity that only needs to be understood when implementing the encoding/decoding. Grouping everything together as a BOUNDS field and having the bounds decoding section describe how this is interpreted would push some of that complexity to a more appropriate subsection.
I think the suggestions from @Timmmm in #23 (comment) makes a lot of sense:
The other thing that I think would make things clearer is a separate diagram for E=0, but that can probably wait, or maybe go in a separate explanatory document.
The text was updated successfully, but these errors were encountered: