unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH 1/1] Support mkdtemp via mkdtemp! and scm_mkdtemp
Date: Wed, 30 Dec 2020 17:05:29 -0600	[thread overview]
Message-ID: <87pn2q28ue.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <20201230084122.GA824833@spikycactus.com>

Mike Gran <spk121@yahoo.com> writes:

> Since mkdtemp already returns a string of the new directory name,
> it might be more scheme-like to not modify the input string, and instead
> just return the new directory name.

Perhaps, though I was just matching the existing semantics of guile
mkstemp, i.e. figured maybe they should behave the same.

> Also, I don't know how universal mkdtemp is. It does exist in Linux and
> OpenBSD, but, I'm not sure about all platforms. So a configure check
> might not be amiss.

Yeah I wondered, though it is at least POSIX:

  https://pubs.opengroup.org/onlinepubs/9699919799/functions/mkdtemp.html

Not sure what our current bar is for checks.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



  reply	other threads:[~2020-12-30 23:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30  1:50 [PATCH 1/1] Support mkdtemp via mkdtemp! and scm_mkdtemp Rob Browning
2020-12-30  8:41 ` Mike Gran
2020-12-30 23:05   ` Rob Browning [this message]
2021-01-05  0:42     ` Rob Browning
2021-01-11 14:04       ` Mike Gran
2021-01-13  0:34         ` Rob Browning
2021-01-19 14:04           ` Mike Gran
2020-12-30  8:45 ` [PATCH] New procedure mkdtemp to create unique directory names Mike Gran via Developers list for Guile, the GNU extensibility library

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=87pn2q28ue.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=spk121@yahoo.com \
    /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).