Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add EBML-ELEMENT-VALID-RANGE test #183

Merged
merged 3 commits into from May 18, 2017

Conversation

dericed
Copy link
Contributor

@dericed dericed commented May 17, 2017

if there is a float range test using hexadecimal floating point
constants which is not '> 0x0p+0’, then the outcome of the test will
be ‘untested’

if there is a float range test using hexadecimal floating point
constants which is not '> 0x0p+0’, then the outcome of the test will
be ‘untested’
it is superseded by EBML-ELEMENT-VALID-RANGE
@dericed dericed force-pushed the EBML-ELEMENT-VALID-RANGE-test branch from 0f70bff to 10a4a74 Compare May 17, 2017 21:25
@dericed
Copy link
Contributor Author

dericed commented May 17, 2017

I fixed a few parts in the wording. Should be ready to merge.

@JeromeMartinez JeromeMartinez merged commit 7690044 into master May 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants