unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Some non-standard O_* flags are missing
Date: Wed, 10 Mar 2021 21:08:20 +0100	[thread overview]
Message-ID: <87lfau22mj.fsf@pobox.com> (raw)
In-Reply-To: <17e5d28f64768602b6e1eb164e82f90b58c5209d.camel@telenet.be> (Maxime Devos's message of "Tue, 09 Mar 2021 22:47:20 +0100")

Heya :)

On Tue 09 Mar 2021 22:47, Maxime Devos <maximedevos@telenet.be> writes:

> On Tue, 2021-03-09 at 21:36 +0100, Andy Wingo wrote:
>> Hi :)  Sure, would be happy to accept a patch for these.
> See <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46220>
> and messages above.  I'll look at updating NEWS and the manual
> later.

Great!

I agree it's weird that O_NOTRANS is defined but 0 on GNU/Linux.
Perhaps better not to define it if it's zero?  Dunno tho.

>>   It's adding
>> more definitions to the base environment, which is usually a negative,
>> but we'll have to find some kind of module solution for all of these
>> flags at some point.
>
> Would defining O_* in a new module (ice-9 open-flags)
> (or the existing module (ice-9 posix) maybe?) be acceptable?
> Or alternatively, a syntax (open-flag SYMBOL) that expands to
> the flag's value --

Let's punt for now :)

>>   If you do send a patch, please update the manual
>> and NEWS also.
>
> The manual only documents O_RDONLY, O_WRONLY, O_RDWR,
> O_APPEND and O_CREAT currently, and points the reader
> at glibc's manual for additional flags.

Ah yes.  Probably the flags (possibly) supported by Guile should be in
the manual.  Document them if you have a moment? :)  Otherwise just
document the new ones.

Andy



      reply	other threads:[~2021-03-10 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 21:13 Some non-standard O_* flags are missing Maxime Devos
2021-03-09 20:36 ` Andy Wingo
2021-03-09 21:47   ` Maxime Devos
2021-03-10 20:08     ` Andy Wingo [this message]

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/guile/

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

  git send-email \
    --in-reply-to=87lfau22mj.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).