Re: EBML specification component for review - Element Data Size
Moritz Bunkus <[email protected]>
| Newsgroups | gmane.comp.multimedia.matroska.devel |
|---|---|
| Message-ID | <[email protected]> |
Hey, > 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. Kind regards, mosu _______________________________________________ Matroska-devel mailing list [email protected] http://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel Read Matroska-Devel on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.devel
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJVQ3vXAAoJEHSvAK3y4yyF0P4P/A23D4B1s10PKjAlDJBrpML8 GTD76UEXu5biQRUTOcbiqJ0pHXMCRGBRZ45w1R/8y3zgbRzli7dXFTXH6mRxvP9u 4dJAMAYEHxpjG4KBQU2HBgzKlD/Vx8pTilJwAi+lIeQl+uUqe71Q5iOFlOsv95vb DWmjfvBdl6TtP15Sa/1UBSuc9iH4y1lEeulymA+WH3BesjwwsN6RtkolpJ/swiqb SIc76yXDhEP+mC8P417fb1dpwzrkp0vycWE/940p0x3gHIhqX0z3v5MRuUXWQTc9 9DLUtlbLmtY52A07dN0jxO4VlEtdbDQIK51TaS/VJVmhqQMLXuAepvBxim7skamb K08zlJJB61xZLJZV/cwFVSJ0eqhByuWbhbIB3mZWAJB5Dyqa1XL7WANWGcktAnD4 Aoku5DtkUY3G8TXsGz9iKe5xf9yRLNkkX5NCY0k+0xRu4LuAdAPHVBXfd/lQV1ug g7/njhooeRTUZJAwXXnxS1oOYQsNZwGw8khElbU48Glu3A8xx94h1klq+GoAXqdp yqF4HCeKPRpMsr7dEPHPLqADEs2Xu0HCa5fx9g5sQOuuu4wBlnvttDnmfeN1qN8C rMX6Xn21SH1iyhhaR58f6Xl1Qqt2UWz/OH9HrShWdwOnuCh/NUbPE74C8BIZr1RQ b6brMKn0KY7fIFKJr7bH =ADBV -----END PGP SIGNATURE-----