From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: native Win32 guile 1.7.0
Date: Fri, 30 May 2003 09:23:41 +1000 [thread overview]
Message-ID: <87he7dnxqa.fsf@zip.com.au> (raw)
In-Reply-To: <87of1lny7w.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 30 May 2003 09:13:07 +1000")
I wrote:
>
> It's usually best to just omit prototypes
No, forget that, I was looking at the wrong bit. (Still true that
it's best to omit, but not when it's one's own defined function :-)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-29 23:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 14:31 native Win32 guile 1.7.0 stefan
2003-05-29 23:13 ` Kevin Ryde
2003-05-29 23:23 ` Kevin Ryde [this message]
2003-05-30 3:23 ` stefan
2003-05-30 23:58 ` Kevin Ryde
2003-06-11 23:42 ` Kevin Ryde
2003-05-30 9:27 ` stefan
2003-05-31 0:20 ` Kevin Ryde
2003-06-08 22:03 ` Kevin Ryde
2003-06-11 23:15 ` Kevin Ryde
2003-06-12 5:01 ` stefan
2003-06-15 0:15 ` putenv tests (was: native Win32 guile 1.7.0) Kevin Ryde
2003-06-11 23:54 ` native Win32 guile 1.7.0 Kevin Ryde
2003-06-14 5:36 ` stefan
2003-06-14 12:24 ` Marius Vollmer
2003-06-14 13:46 ` stefan
2003-06-14 16:18 ` Marius Vollmer
2003-06-16 17:25 ` stefan
2003-06-18 23:42 ` Marius Vollmer
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=87he7dnxqa.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).