NetBSD Problem Report #47616

From www@NetBSD.org  Mon Mar  4 12:44:21 2013
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 47C1C63F145
	for <gnats-bugs@gnats.NetBSD.org>; Mon,  4 Mar 2013 12:44:21 +0000 (UTC)
Message-Id: <20130304124420.4FB1063F145@www.NetBSD.org>
Date: Mon,  4 Mar 2013 12:44:20 +0000 (UTC)
From: sdaoden@gmail.com
Reply-To: sdaoden@gmail.com
To: gnats-bugs@NetBSD.org
Subject: Manuals backdate multibyte functions to ANSI C, though A stands for American (the "big ten inch")
X-Send-Pr-Version: www-1.0

>Number:         47616
>Category:       standards
>Synopsis:       Manuals backdate multibyte functions to ANSI C, though A stands for American (the "big ten inch")
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    standards-manager
>State:          closed
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 04 12:45:00 +0000 2013
>Closed-Date:    Mon Sep 09 01:06:10 +0000 2024
>Last-Modified:  Mon Sep 09 01:06:10 +0000 2024
>Originator:     Steffen Daoden (through the grapevine) (Godzilla)
>Release:        6.99.16
>Organization:
>Environment:
/jsonn/src, trunk/
>Description:
Manuals falsely claim Ansi C.
I still don't know what is correct, but simply assumed that the presence of a function in lib/libc/locale/multibyte_*.c is correct.
Aaand i also found the addendum macro itmw.
>How-To-Repeat:

>Fix:
diff -Napru lib_libc_locale.orig/mblen.3 lib_libc_locale/mblen.3
--- lib_libc_locale.orig/mblen.3	2013-03-04 13:21:33.000000000 +0100
+++ lib_libc_locale/mblen.3	2013-03-04 13:23:13.000000000 +0100
@@ -177,4 +177,4 @@ points to an invalid or incomplete multi
 The
 .Fn mblen
 function conforms to
-.St -ansiC .
+.St -isoC .
diff -Napru lib_libc_locale.orig/mbstowcs.3 lib_libc_locale/mbstowcs.3
--- lib_libc_locale.orig/mbstowcs.3	2013-03-04 13:21:33.000000000 +0100
+++ lib_libc_locale/mbstowcs.3	2013-03-04 13:24:32.000000000 +0100
@@ -124,6 +124,6 @@ points to a string containing an invalid
 The
 .Fn mbstowcs
 function conforms to
-.St -ansiC .
+.St -isoC .
 The restrict qualifier is added at
 .St -isoC-99 .
diff -Napru lib_libc_locale.orig/mbtowc.3 lib_libc_locale/mbtowc.3
--- lib_libc_locale.orig/mbtowc.3	2013-03-04 13:21:33.000000000 +0100
+++ lib_libc_locale/mbtowc.3	2013-03-04 13:24:44.000000000 +0100
@@ -177,6 +177,6 @@ points to an invalid or incomplete multi
 The
 .Fn mbtowc
 function conforms to
-.St -ansiC .
+.St -isoC .
 The restrict qualifier is added at
 .St -isoC-99 .
diff -Napru lib_libc_locale.orig/wcsrtombs.3 lib_libc_locale/wcsrtombs.3
--- lib_libc_locale.orig/wcsrtombs.3	2013-03-04 13:21:33.000000000 +0100
+++ lib_libc_locale/wcsrtombs.3	2013-03-04 13:25:23.000000000 +0100
@@ -171,6 +171,6 @@ points to a string containing an invalid
 The
 .Fn wcsrtombs
 function conforms to
-.St -ansiC .
+.St -isoC-amd1 .
 The restrict qualifier is added at
 .St -isoC-99 .
diff -Napru lib_libc_locale.orig/wcstombs.3 lib_libc_locale/wcstombs.3
--- lib_libc_locale.orig/wcstombs.3	2013-03-04 13:21:33.000000000 +0100
+++ lib_libc_locale/wcstombs.3	2013-03-04 13:25:38.000000000 +0100
@@ -128,6 +128,6 @@ points to a string containing an invalid
 The
 .Fn wcstombs
 function conforms to
-.St -ansiC .
+.St -isoC .
 The restrict qualifier is added at
 .St -isoC-99 .
diff -Napru lib_libc_locale.orig/wctomb.3 lib_libc_locale/wctomb.3
--- lib_libc_locale.orig/wctomb.3	2013-03-04 13:21:33.000000000 +0100
+++ lib_libc_locale/wctomb.3	2013-03-04 13:28:47.000000000 +0100
@@ -128,4 +128,4 @@ No errors are defined.
 The
 .Fn wctomb
 function conforms to
-.St -ansiC .
+.St -isoC .

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Mon, 09 Sep 2024 01:06:10 +0000
State-Changed-Why:
I can't easily find a copy of the actual ANSI C standard, but from the
drafts I can find, it looks like these functions originated in ANSI C
and not in ISO C.  For example, they're already here in this 1988
draft of the ANSI C standard:
https://web.archive.org/web/20161223125339/http://flash-gordon.me.uk/ansi.c.txt

If there's a better authority for this (if someone goes to the trouble
of finding a copy behind the paywalls) that shows it should be ISO C90
and not ANSI C89, we can fix  this, but until then it looks to me like
the man pages are correct as is.


>Unformatted:

Home	PR Database Search