From: "Maciej W. Rozycki" <macro@wdc.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc at the Toolchains microconference at LPC 2019
Date: Sat, 14 Sep 2019 05:33:03 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.1909140528320.28360@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <87lfwukzw9.fsf@oldenburg2.str.redhat.com>
On Fri, 19 Jul 2019, Florian Weimer wrote:
> > I suggest using "ssize_t or size_t" to keep the text parallel with
> > "int or unsigned int". We shouldn't insist on size_t for buffer sizes
> > when the natural interpretation of the value is signed (as in the
> > return value for 'read' etc.) or is too large for malloc etc.
>
> Right. Incoming buffer sizes should be size_t (no in-band signaling).
> Return values tend to have in-band signaling for errors and thus need to
> be ssize_t.
FYI, the response was positive and a rough transcript of the session is
available from <https://etherpad.net/p/LPC2019_TC>. I'll be there at the
glibc BoF available to comment.
Maciej
next prev parent reply other threads:[~2019-09-14 4:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 16:01 glibc at the Toolchains microconference at LPC 2019 Florian Weimer
2019-06-26 16:39 ` Dmitry V. Levin
2019-06-26 16:50 ` Zack Weinberg
2019-06-26 16:56 ` Florian Weimer
2019-06-26 17:40 ` Zack Weinberg
2019-06-26 20:33 ` Carlos O'Donell
2019-06-26 20:39 ` Christian Brauner
2019-06-26 20:58 ` Carlos O'Donell
2019-06-26 17:28 ` Yann Droneaud
2019-06-26 17:41 ` Christian Brauner
2019-06-26 21:04 ` Carlos O'Donell
2019-06-27 9:39 ` Dmitry V. Levin
2019-06-27 10:05 ` Szabolcs Nagy
2019-06-27 10:18 ` Christian Brauner
2019-06-27 13:05 ` Dmitry V. Levin
2019-06-27 15:57 ` Zack Weinberg
2019-06-27 17:21 ` Florian Weimer
2019-06-27 20:07 ` Carlos O'Donell
2019-06-27 20:53 ` wrappers for multiplexed syscalls (was Re: glibc at the Toolchains microconference at LPC 2019) Dmitry V. Levin
2019-06-27 21:22 ` Florian Weimer
2019-06-28 21:20 ` Dmitry V. Levin
2019-06-28 21:35 ` Florian Weimer
2019-06-29 1:52 ` Zack Weinberg
2019-06-29 6:27 ` Florian Weimer
2019-06-27 13:22 ` glibc at the Toolchains microconference at LPC 2019 Zack Weinberg
2019-06-27 14:10 ` syscall wrappers policy (was re: glibc at the Toolchains microconference) Zack Weinberg
2019-06-27 15:48 ` DJ Delorie
2019-06-27 16:02 ` Zack Weinberg
2019-06-27 16:50 ` Carlos O'Donell
2019-06-27 17:45 ` glibc at the Toolchains microconference at LPC 2019 Maciej Rozycki
2019-07-08 12:57 ` Florian Weimer
2019-07-08 16:06 ` Paul Eggert
2019-07-19 11:49 ` Florian Weimer
2019-09-14 4:33 ` Maciej W. Rozycki [this message]
2019-09-14 11:53 ` Dmitry V. Levin
2019-09-14 14:02 ` Maciej W. Rozycki
2019-07-09 0:14 ` Dmitry V. Levin
2019-09-16 13:26 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.1909140528320.28360@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).