Re: Bytes & Chars

Article View: comp.std.c

Article #3987

#3987

From: Thad Smith
Date: Wed, 13 Sep 1995 19:54

16 lines
1261 bytes

In article <DEu4Ep.76H@ukpsshp1.serigate.philips.nl>,
baynes@ukpsshp1.serigate.philips.nl (Stephen Baynes) wrote:

>It gets worse I have just looked at the section on memcpy, 7.11.2.1, [as given
>in Plauger's book]. This says "The memcpy function copies n characters...". 
...
>I think there might be material for a defect report here about the use
>of "n characters". I think that should be either "n bytes" or "n chars" or
>"an object of size n". The last would be more consistant with the wording
>for malloc (7.10.3.3) and fread (7.9.8.1). Anyone else care to comment?

I agree with this comment about n bytes being more precise.  The last
option doesn't seem right because memcpy() can work on partial objects
or multiple objects as well as a single object.

Thad

Technical Details

Message-ID: <+axVwQ9ytR3d084yn@csn.net>

Path: arc1-ca.pugleaf.net!teal.csn.net!not-for-mail

References:

<DDvt89.Jx5@sco.COM> <41nkl7$h53@newsbf02.news.aol.com> <42vd3s$t58@news.cs.tu-berlin.de> <DEs7JA.892@ukpsshp1.serigate.philips.nl> <DEu4Ep.76H@ukpsshp1.serigate.philips.nl>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!teal.csn.net!not-for-mail
From: thads@csn.net (Thad Smith)
Newsgroups: comp.std.c
Subject: Re: Bytes & Chars
Date: 13 Sep 1995 13:54:09 -0600
Organization: T3 Systems
Message-ID: <+axVwQ9ytR3d084yn@csn.net>
References: <DDvt89.Jx5@sco.COM> <41nkl7$h53@newsbf02.news.aol.com>
 <42vd3s$t58@news.cs.tu-berlin.de> <DEs7JA.892@ukpsshp1.serigate.philips.nl>
 <DEu4Ep.76H@ukpsshp1.serigate.philips.nl>
Reply-To: ThadSmith@acm.org
NNTP-Posting-Host: 199.117.27.22

Reply to Parent Message