[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 0001646. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 792. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 0001524. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 0001526. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 609. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 0001428. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare

Re: Use of "negative" in pow() ERRORS (was: [1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17)

On 2020-11-12 10:05:16 +, Geoff Clare via austin-group-l at The Open Group wrote: > The problem is that the phrase "negative zero" is commonly used to > mean -0.0, so some people naturally assume that "negative" on its > own includes "negative zero". In the IEEE 754-2019 standard, "negative

Re: Use of "negative" in pow() ERRORS (was: [1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17)

Vincent Lefevre wrote, on 11 Nov 2020: > > On 2020-11-09 09:39:25 +, Geoff Clare via austin-group-l at The Open > Group wrote: > > I believe this is a misuse of "negative". The RETURN VALUE section > > says "For finite values of x < 0, and finite non-integer values of y, > > a domain error

Re: Use of "negative" in pow() ERRORS (was: [1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17)

On 2020-11-09 09:39:25 +, Geoff Clare via austin-group-l at The Open Group wrote: > I believe this is a misuse of "negative". The RETURN VALUE section > says "For finite values of x < 0, and finite non-integer values of y, > a domain error shall occur ..." > > So the ERRORS section should

Use of "negative" in pow() ERRORS (was: [1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17)

> -- > (0005108) nick (manager) - 2020-11-08 23:42 > https://austingroupbugs.net/view.php?id=1302#c5108 > -- > The following issue was pointed out by Hubert

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assigned To: