🚀 go-pugleaf

In article <DnFr78.1wo@ukpsshp1.serigate.philips.nl>
baynes@ukpsshp1.serigate.philips.nl (Stephen Baynes) writes:

SB: Tanmoy Bhattacharya (tanmoy@qcd.lanl.gov) wrote:
SB: : In article <4gr3d1$dca@usenet.pa.dec.com>
SB: : diamond@tbj.dec.com (Norman Diamond) writes:
SB: <snip - copying data by using chars of different sorts vs memcpy >
SB: : This was a free-standing implementation, and memcpy may be absent. (In
SB: : a hosted implementation, as all read/write is done as if through
SB: : getc/putc which handles unsigned char values, and binary files written
SB: : out must be read back unchanged, the situation is impossible).
SB: 
SB: That read/write is done by getc/putc does not imply very much about copying
SB: chars. I don't see any requirement that fwrite/fread use one putc/getc per
SB: byte(ie char) of memory. Fwrite could use one per bit writing the
values 'Y' or 
SB: 'N' if it wanted so long as fread will read it back again. My
understanding 
SB: is that the use of getc/putc means you can write a file with
fwrite, copy it 
SB: with getc/putc and read the copy with fread to get what you started with.

I understood it to mean that I could take the same (void*) pointer to
the data, and call putc repeatedly on the successive bytes of the
data, and the resulting file is identical to doing an fwrite. I think
the standard should clarify its meaning.

Cheers
Tanmoy
--
tanmoy@qcd.lanl.gov(128.165.23.46) DECNET: BETA::"tanmoy@lanl.gov"(1.218=1242)
Tanmoy Bhattacharya O:T-8(MS B285)LANL,NM87545 H:#9,3000,Trinity Drive,NM87544
Others see <gopher://yaleinfo.yale.edu:7700/00/Internet-People/internet-mail>,
<http://alpha.acast.nova.edu/cgi-bin/inmgq.pl>or<ftp://csd4.csd.uwm.edu/pub/
internetwork-mail-guide>. -- <http://nqcd.lanl.gov/people/tanmoy/tanmoy.html>
fax: 1 (505) 665 3003   voice: 1 (505) 665 4733    [ Home: 1 (505) 662 5596 ]