src-test2/lib/libc/locale/isdigit.3, branch release/8.1.0

- Fix typo

2007-05-04T16:01:07Z

Approved by: keramida (mentor) MFC after: 3 days

Per Regents of the University of Calfornia letter, remove advertising

2007-01-09T00:28:16Z

clause. # If I've done so improperly on a file, please let me know.

-mdoc sweep.

2005-11-17T13:00:00Z

Remove confusing "single C char locales" phrase; arguments to these

2005-07-17T04:11:06Z

functions and must now be either an unsigned char or EOF, regardless of locale.

Re-word compatibility section, taking care to use the word "obsolete" to

2004-08-21T07:37:08Z

describe the 4.4BSD extension of accepting characters (runes) outside of the range of unsigned char.

Re-word the COMPATIBILITY section, taking care to use the word "deprecated"

2004-07-29T23:32:41Z

to describe the 4.4BSD extension of accepting arguments outside the range of unsigned char. This gives us freedom to remove this extension when we remove the interface in FreeBSD 6.

Document the isnumber() and ishexnumber() functions, and explain how they

2004-03-30T07:02:04Z

differ (at least in theory) from isdigit() and isxdigit().

Add a note to the Compatiblity section suggesting that these functions

2002-10-06T10:15:38Z

only be used for byte values. Add cross-references to the wide-char counterparts.

From the PR:

2002-01-09T13:43:31Z

1. ctype.h defines digittoint(), isnumber() and ishexnmber(), yet they are not documented in any of the manpages. 2. The ctype manpage references a non-existent manpage for digittoint(). 3. The isascii() manpage claims it is standards compliant, when it isn't. 4. isblank() claims it is _not_ standards compliant, when it is. Fix by including the appropriate .Nm entries, and with a new digittoint.3 page. PR: docs/26451 Submitted by: Adrian Filipi-Martin

Clarify that is[x]digit() class is the same in any locale

2001-11-29T15:23:46Z