Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!rit!cci632!ccicpg!hobbit!ndjc
From: ndjc@hobbit.UUCP (Nick Crossley)
Newsgroups: comp.std.c
Subject: Re: How ANSI is Apollo's cc 6.7 (SR 10.2)
Summary: isn't strcpyn reserved?
Message-ID: <86589@hobbit.UUCP>
Date: 11 Sep 90 17:19:04 GMT
References: <15434@reed.UUCP> <13798@smoke.BRL.MIL>
Organization: ICL North America, Irvine, CA 92718
Lines: 16

In article <13798@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
>>(from string.h - this is wrapped inside of an '#ifdef __STDC__')
>>extern char *strcpyn(...);
>
>Actually, this should be EXCLUDED when __STDC__ is in effect, since
>the C standard prohibits inclusion of arbitrary junk in standard
>headers for a conforming (__STDC__) implementation.

I thought all external names starting str[a-z]... were reserved to the
implementation for future ANSI C string functions, so is strcpyn()
really illegal?
-- 

<<< standard disclaimers >>>
Nick Crossley, ICL NA, 9801 Muirlands, Irvine, CA 92718-2521, USA 714-458-7282
uunet!ccicpg!ndjc  /  ndjc@ccicpg.UUCP