bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] read-file: add variants that clear internal memory
Date: Tue, 26 May 2020 20:33:34 +0200	[thread overview]
Message-ID: <1883606.oFhN3a00iB@omega> (raw)
In-Reply-To: <87pnaqejxa.fsf-ueno@gnu.org>

Hi Daiki,

> > If you agree, I'd like to see two commits:
> >   1. the introduction of the flags and RF_BINARY,
> >   2. the RF_SENSITIVE flag.
> >
> > Do you want me to code the first commit, or do you want to do it?
> 
> Sure, that would make things much simpler.  I'm attaching a patch along
> these lines.

It would be useful to first concentrate on the first part, the refactoring
that introduces flags and RF_BINARY. This would provide a patch that is easier
to review and does not have the following problems:
  - internal_fread_file still exists, although fread_file is a no-op wrapper
    around it.
  - In tests/test-read-file.c, please terminate the main() function with a
    return statement. We assume C99 only in modules that explicitly list 'c99'
    as a dependency. If it's trivial to avoid this dependency, let's do it.
  - The NEWS file needs an entry.

Bruno



  reply	other threads:[~2020-05-26 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  8:35 [PATCH] read-file: add variants that clear internal memory Daiki Ueno
2020-05-26 10:54 ` Bruno Haible
2020-05-26 16:32   ` Daiki Ueno
2020-05-26 18:33     ` Bruno Haible [this message]
2020-05-27  6:43       ` Daiki Ueno
2020-05-27 11:12         ` Bruno Haible
2020-05-27 12:18           ` Daiki Ueno
2020-05-28 20:09             ` Bruno Haible
2020-05-29  3:59               ` Daiki Ueno
2020-05-29  9:15                 ` Bruno Haible
2020-05-29 15:23                   ` Daiki Ueno

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1883606.oFhN3a00iB@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=ueno@gnu.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).