From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Help, Guidance for Guile Module Builders
Date: 16 Mar 2002 00:13:15 +0000 [thread overview]
Message-ID: <m3y9gtl690.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <878z8ty8mf.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us>
>>>>> "Evan" == Evan Prodromou <evan@glug.org> writes:
Evan> So, I'd like to assemble some kind of document that gives
Evan> "recommended" coding suggestions for Guile modules -- especially those
Evan> that aspire to participation in GUMM.
Sounds great. One thought only, I'm afraid - have you checked out all
the autoconf stuff and accompanying docs that thi has recently added
to Guile CVS? Unless I'm misunderstanding something, that should be
an excellent start for what you're aiming at.
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-03-16 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 18:43 Help, Guidance for Guile Module Builders Evan Prodromou
2002-03-16 0:13 ` Neil Jerram [this message]
2002-03-16 4:51 ` Evan Prodromou
2002-03-16 13:22 ` Neil Jerram
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=m3y9gtl690.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@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).