Skip to content

Commit

Permalink
[CLIBABI32] Restore missing reference to EDOM.
Browse files Browse the repository at this point in the history
I just noticed a paragraph that was grammatically confusing because it
contained a comma with no word before it, and an equality with no
left-hand side.

It looks to me as if the <errno.h> macro name EDOM was accidentally
deleted in both cases. (Rationale: EDOM is an error code closely
related to ERANGE, and matches the claim in the paragraph that its
consensus value is 33 – that's its value on Linux, for example.)

Searching for ERANGE in the rest of the document turned up another two
places where there was a missing word that looked as if it ought to be
"EDOM".

I've no idea how this happened! But it seems like an easy fix.
  • Loading branch information
statham-arm authored and smithp35 committed Mar 22, 2024
1 parent 38f7625 commit 7c2fbbd
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions clibabi32/clibabi32.rst
Original file line number Diff line number Diff line change
Expand Up @@ -828,9 +828,9 @@ Grey list items are a little more difficult. There are two options.

- Treat the consensus members as *white* and the remainder as *black*.

Consider , ERANGE, and EILSEQ from errno.h. This is a grey list category
because there is consensus that = 33 and ERANGE = 34, but no consensus
(even among Unix-like implementations) about EILSEQ.
Consider EDOM, ERANGE, and EILSEQ from errno.h. This is a grey list
category because there is consensus that EDOM = 33 and ERANGE = 34,
but no consensus (even among Unix-like implementations) about EILSEQ.

In practice, these values will be rarely accessed by portable code, so
there is no associated performance or size issue, and they should all be
Expand Down Expand Up @@ -1346,8 +1346,8 @@ We define it as shown in `errno.h definitions`_
:class: note

There seems to be general agreement on 33 and 34, the long established Unix
values of and ERANGE. There is little consensus about EILSEQ. 47 is claimed
to be the IEEE 1003.1 POSIX value.
values of EDOM and ERANGE. There is little consensus about EILSEQ. 47 is
claimed to be the IEEE 1003.1 POSIX value.

float.h
-------
Expand Down Expand Up @@ -2104,7 +2104,7 @@ Summary of requirements on C Libraries
+--------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| ctype..h | Yes | Must define **is**\ xxxx(c) to be ((**is**\ xxxx)(c)) etc [no inline implementation] or implement the inline versions as described in `ctype.h when \_AEABI\_PORTABILITY\_LEVEL != 0 and isxxxxx inline`_. |
+--------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| errno.h | Yes | errno is (\*\_\_aeabi\_errno()); , ERANGE, etc are link-time constants (`errno.h definitions`_) |
| errno.h | Yes | errno is (\*\_\_aeabi\_errno()); EDOM, ERANGE, etc are link-time constants (`errno.h definitions`_) |
+--------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| float.h | No | |
+--------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Expand Down

0 comments on commit 7c2fbbd

Please sign in to comment.