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

Editorial: Update IEEE 754 standard version #1770

Open
wants to merge 1 commit into
base: master
from

Conversation

@chicoxyzzy
Copy link
Member

chicoxyzzy commented Nov 6, 2019

Related issue #1650

@PrimerMediaGroup

This comment was marked as spam.

Copy link

PrimerMediaGroup commented Nov 6, 2019

Rename Spacebookclub.com so we don't lose our profile pictures and information

@ljharb ljharb force-pushed the chicoxyzzy:ieee754-2019 branch from 9ec888b to 0b55d81 Nov 7, 2019
@ljharb ljharb requested review from syg, michaelficarra, bakkot and tc39/ecma262-editors Nov 7, 2019
@ljharb
ljharb approved these changes Nov 7, 2019
@ljharb ljharb self-assigned this Nov 7, 2019
@michaelficarra

This comment has been minimized.

Copy link
Member

michaelficarra commented Nov 8, 2019

If there's nothing that affects observable behaviour of ECMAScript programs, what's the motivation to update the normative reference? Sell more copies of IEEE-754?

@apaprocki

This comment has been minimized.

Copy link
Contributor

apaprocki commented Nov 8, 2019

To the contrary, the observable behavior is the fact that the reference has updated with no change, signaling to readers that the spec is and was compatible with both versions. Otherwise, someone could ask themselves “wait, why the old standard?” and spend some amount of time finding the answer.

(An example of that not happening is the C++ normative reference to ES3, where it is not updated because it isn’t compatible with later versions.)

@michaelficarra

This comment has been minimized.

Copy link
Member

michaelficarra commented Nov 8, 2019

@apaprocki Then, for the same reason, we should mention that either will do.

@apaprocki

This comment has been minimized.

Copy link
Contributor

apaprocki commented Nov 9, 2019

What do you think about normatively referencing the 2019 standard, and then providing a "conformance note" (those words) that a 2008 conformant implementation is also acceptable?

Whether or not that extends to say something along the lines of "there are no normative changes between IEEE-754:2008 and IEEE-754:2019 that affect the ECMA-262 specification" is up to the editors.

@chicoxyzzy

This comment has been minimized.

Copy link
Member Author

chicoxyzzy commented Nov 11, 2019

Should this note be added to Bibliography?

@ljharb IPR check is failing. Do I need to do something with this?

@michaelficarra

This comment has been minimized.

Copy link
Member

michaelficarra commented Nov 11, 2019

@apaprocki I would strongly prefer the latter wording.

@ljharb

This comment was marked as resolved.

Copy link
Member

ljharb commented Nov 12, 2019

@chicoxyzzy no; it's not a required check. it currently fails on every PR because there's no way to get encrypted credentials safely into that script. I'm working on removing it from PRs (but leaving it on master) until that's solved; ignore it in the meantime.

@syg
syg approved these changes Nov 13, 2019
Copy link
Member

michaelficarra left a comment

I'd like to see a reference to IEEE 754-2008.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.