Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: Portable 16 bit binary integer write
Date: Sun, 25 Sep 2016 15:17:08 -0700
Organization: None to speak of
Lines: 29
Message-ID: <lnvaxjtyjf.fsf@kst-u.example.com>
References: <50a1e8f4-4fb3-4491-97d0-54768bf28685@googlegroups.com> <b89ceb12-0c5b-4f0f-ad4a-a74d470b56de@googlegroups.com> <nrf2rf$5ha$1@dont-email.me> <0b757bbb-0494-44cb-bd5a-26f117aaa404@googlegroups.com> <nrgcuu$9hr$1@dont-email.me> <2cf666d7-0755-4c70-adad-07dbafc2b2e7@googlegroups.com> <nrhbt5$l7r$1@dont-email.me> <c9cb703c-db1b-4baa-9622-538aeaca5652@googlegroups.com> <lnk2ebzaxe.fsf@kst-u.example.com> <09cb4413-16a6-4b63-89d0-9dafe56562f6@googlegroups.com> <lnfuozz3ea.fsf@kst-u.example.com> <68e53f3a-5fcc-44fc-90c4-bcf8dc3db680@googlegroups.com> <ln7faayyhf.fsf@kst-u.example.com> <kfnh998fuoa.fsf@x-alumni2.alumni.caltech.edu> <ns02d8$5cl$1@dont-email.me> <kfn60pme9ki.fsf@x-alumni2.alumni.caltech.edu> <dd711aca-f51f-4304-a55d-c9192c811c64@googlegroups.com> <lnbmzduhlr.fsf@kst-u.example.com> <c0983f56-2a98-4a93-82ea-0d7de6324228@googlegroups.com> <87y42ge0gy.fsf@bsb.me.uk> <e27b618e-5dc1-4ef0-89f4-e9329150943d@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="30697"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+E+fKiEdc9UCcsoqk/pgEx"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:HfLE5ACBenUoGAXOcfIRlLa7y8M= sha1:Hqg86hCu1vm2xMMODkMfMZiZB58=
Xref: csiph.com comp.lang.c:94059

supercat@casperkitty.com writes:
> On Sunday, September 25, 2016 at 5:29:57 AM UTC-5, Ben Bacarisse wrote:
>> Or you could have two functions and use a format specifier.  That could
>> be made considerably more flexible.  And, at the expense of a bit more
>> bloat, one could even add this to printf/scanf families.
>
> Back around 1990 I remember thinking there should be printf/scanf-like
> functions for binary data (they'd need to be separate functions because
> printf and scanf aren't designed to accommodate data that may contain
> zero bytes, newlines, etc.

printf("%c", 0) prints a null byte.  putchar('\n') prints a newline.
What's the problem?

You can't have an embedded null character in a format string or in a
string pointed by an argument corresponding to a "%s" format, but apart
from that fprintf and fscanf certainly can deal with zero bytes and
newline.  It's not common to use fprintf with a binary stream, but it's
well defined.  (I'm assuming that you're really referring to fprintf and
fscanf, and not literally to printf and scanf which work with stdout and
stdin, which are opened in text mode.)

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"