[Matroska-devel] EBML specification component for review - Element Data Size
moritz at bunkus.org
Fri May 1 15:12:55 CEST 2015
> Actually, handling unknown sizes seems to make parsing significantly
> harder. Tracking the boundary of the end of the current parent segment
> is not enough. You also have to keep track which elements are
> (theoretically) possible at all in a given context, so you can
> properly switch back to the grandparent segment if an element is
> specified not to be possible in the current segment.
I see your point. Limiting the use in some way seems like a good thing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the Matroska-devel