From: Thien-Thi Nguyen <ttn@glug.org>
Cc: guile-user@gnu.org
Subject: Re: cmod-play 1 available + modsup.h additions
Date: Fri, 14 Nov 2003 08:10:32 -0500 [thread overview]
Message-ID: <E1AKdia-0000cx-00@colo.agora-net.com> (raw)
In-Reply-To: <20031114082656.GE14359@powergnu.laas.fr> (message from Ludovic Courtès on Fri, 14 Nov 2003 09:26:58 +0100)
From: Ludovic =?iso-8859-1?Q?Court=E8s?= <ludovic.courtes@laas.fr>
Date: Fri, 14 Nov 2003 09:26:58 +0100
The naming style of the macros in modsup.h doesn't seem to be very
consistent with the rest of the API. In particular, macros are not
defined in the SCM_ namespace and their name are pretty concise
(abbreviations, no underscores in between words, etc.).
i'd like to keep them out of SCM_ namespace, actually, and tried for the
"M" namespace, which is admittedly easy to stumble on inadvertantly by
other code. guile 1.4.x has SCM_ and GH_ already, maybe GHM_ (for guile
high-level "module support") is better. how does that sound?
Also, will this be part of Guile 1.6.x too?
since it's an additive change, introducing these macros does not raise
compatibility issues, but of course there may be other criterion by
which they will be rejected. there's a lot of stuff in 1.4.x[1] that
could easily be added to other guile branches but the will to do so has
not yet materialized (and might never). that's not something i can
control so i don't worry about it, generally.
thi
________________________________________________________
[1] for example, machine assisted doc maintenance:
http://www.glug.org/docbits/guile/1.4.x/Doc-Maintenance.html
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-11-14 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 21:55 cmod-play 1 available + modsup.h additions Thien-Thi Nguyen
2003-11-14 8:26 ` Ludovic Courtès
2003-11-14 13:10 ` Thien-Thi Nguyen [this message]
2003-11-14 13:37 ` Ludovic Courtès
2003-11-14 17:38 ` Thien-Thi Nguyen
2003-11-14 14:29 ` Marius Vollmer
2003-11-14 14:17 ` Marius Vollmer
2003-11-14 15:28 ` Does anyone have a better scm_string_hash ? Roland Orre
2003-11-14 15:51 ` Ludovic Courtès
2003-11-17 8:33 ` Roland Orre
2003-11-17 13:01 ` Ludovic Courtès
2003-11-17 15:42 ` Marius Vollmer
2003-11-17 16:02 ` Marius Vollmer
2003-11-17 16:29 ` Marius Vollmer
2003-11-17 16:48 ` Allister MacLeod
2003-11-17 17:57 ` Marius Vollmer
2003-11-17 19:17 ` OT: x86 assembly timings/size (was Re: Does anyone have a better scm_string_hash ?) Allister MacLeod
2003-11-17 21:27 ` OT: x86 assembly timings/size Marius Vollmer
2003-11-19 9:04 ` Does anyone have a better scm_string_hash ? Ludovic Courtès
2003-11-19 15:02 ` Marius Vollmer
2003-11-14 17:40 ` cmod-play 1 available + modsup.h additions Thien-Thi Nguyen
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=E1AKdia-0000cx-00@colo.agora-net.com \
--to=ttn@glug.org \
--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).