unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: Bill Schottstaedt <bil@ccrma.stanford.edu>, guile-devel@gnu.org
Subject: Re: file-exists? confused
Date: Wed, 29 Mar 2006 11:45:10 +1100	[thread overview]
Message-ID: <87mzfayt7t.fsf@zip.com.au> (raw)
In-Reply-To: <87slp6qgyn.fsf@minimini.mvo.home> (Marius Vollmer's message of "26 Mar 2006 00:48:00 +0200")

Marius Vollmer <mvo@zagadka.de> writes:
>
>> There doesn't seem to be any room in that struct, but if it's always
>> created by scm_make_port_type then perhaps adding new fields to the
>> end would keep compatibility.
>
> Yes, that is good enough.

I might do something for stat and readdir first, then that struct.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2006-03-29  0:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 16:55 file-exists? confused Bill Schottstaedt
2006-03-13 21:17 ` Kevin Ryde
2006-03-14 22:33   ` Kevin Ryde
2006-03-25 22:48     ` Marius Vollmer
2006-03-29  0:45       ` Kevin Ryde [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=87mzfayt7t.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=bil@ccrma.stanford.edu \
    --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).