From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: delete-file ??
Date: Mon, 15 Jul 2002 01:00:44 -0500 [thread overview]
Message-ID: <87n0stwmwj.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <3D31A7BD.F6BA53F1@pacbell.net> (Bruce Korb's message of "Sun, 14 Jul 2002 09:33:01 -0700")
Bruce Korb <bkorb@pacbell.net> writes:
> Programming successfully is a task involving keeping track of
> a myriad of minutia and fitting all the little pieces together.
> Anything that reduces the amount of information that one needs
> to track is a good thing. The Guile library supports POSIX
> calls with POSIX-ly named functions. Excellent. I only need
> to learn one set of names and figure out some mostly obvious
> permutations to use the Guile function for the POSIX call.
> So, despite the fact that "delete-file" is far more obvious
> than "unlink", the rename increases the complexity of my
> programming life. I had to find "delete-file" by grepping
> the source for "unlink *\(". Ick. Please consider adding
> "unlink" and any other POSIX calls that got renamed.
That sounds like a good idea to me, though we might need another
function. I'm not sure what the error/return semantics of delete-file
are -- docs don't say, and whatever's bound to unlink should follow
the current guile posix conventions...
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-15 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 16:33 delete-file ?? Bruce Korb
2002-07-15 6:00 ` Rob Browning [this message]
2002-07-16 0:03 ` Bruce Korb
2002-07-16 1:56 ` Rob Browning
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=87n0stwmwj.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).