Skip to content

Use the EbmlDocVersion constraints when checking/adding mandatory elements #277

Description

@robUx4

Although we don't do that (yet ?) in Matroska, it's possible to add new mandatory elements without a default value. Such elements should not be written when writing an older version of the doctype. They should also not be automatically added to an EbmlMaster by default.

This will require passing the EbmlDocVersion in more places. Or probably introduce a ShouldRead function which could do more than just checking the profile, for example allow dummy elements or not. Just like ShouldWrite is used to skip the elements with a default value.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    api-breakbreaks the API (e.g. programs using it will have to adjust their source code)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions