From: Mark H Weaver <mhw@netris.org>
To: Andy Wingo <wingo@pobox.com>
Cc: Bruce Korb <bruce.korb@gmail.com>, guile-devel@gnu.org
Subject: Re: unknown location: definition in expression context in subform optname-from of "_^"
Date: Sun, 29 Jan 2012 16:32:28 -0500 [thread overview]
Message-ID: <87y5sqjitv.fsf@netris.org> (raw)
In-Reply-To: <87aa56z21j.fsf@pobox.com> (Andy Wingo's message of "Sun, 29 Jan 2012 21:28:24 +0100")
Andy Wingo <wingo@pobox.com> writes:
> Keyword arguments suit this task much better.
Okay, I have a fresh idea for your consideration.
Let's provide a more general facility to make keyword arguments more
convenient to use from C, while avoiding repeatedly interning them. I
propose a new macro SCM_KEYWORD, which would be defined something like
this:
#ifdef __GNUC__
# define SCM_KEYWORD(name) \
({ static SCM keyword = SCM_BOOL_F; \
if (SCM_UNLIKELY (scm_is_false (keyword))) \
keyword = scm_from_utf8_keyword (#name); \
return keyword; })
#else
# define SCM_KEYWORD(name) scm_from_utf8_keyword (#name)
#endif
Furthermore, at some point in the future we could provide an optional
alternative mechanism, where SCM_KEYWORD would expand into a simple
global variable reference, and we'd provide a snarfing script to scan
the sources for SCM_KEYWORD and produce an initialization routine for
all these global keywords.
It might be good to do something similar for looking up and caching
scheme procedures as well.
What do you think?
Mark
next prev parent reply other threads:[~2012-01-29 21:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 3:56 unknown location: definition in expression context in subform optname-from of "_^" Bruce Korb
2012-01-26 4:22 ` Mike Gran
2012-01-26 5:31 ` David Kastrup
2012-01-26 21:05 ` Bruce Korb
2012-01-26 21:21 ` Mike Gran
2012-01-26 21:37 ` Bruce Korb
2012-01-27 0:10 ` Mark H Weaver
2012-01-27 0:56 ` Bruce Korb
2012-01-27 2:26 ` Mark H Weaver
2012-01-27 2:44 ` Bruce Korb
2012-01-27 2:59 ` Noah Lavine
2012-01-27 3:36 ` Bruce Korb
2012-01-28 7:02 ` Mark H Weaver
2012-01-28 16:58 ` Bruce Korb
2012-01-28 19:03 ` Andy Wingo
2012-01-28 19:47 ` Mark H Weaver
2012-01-28 22:58 ` Andy Wingo
2012-01-29 4:12 ` Mark H Weaver
2012-01-29 17:40 ` Bruce Korb
2012-01-29 18:06 ` Mike Gran
2012-01-29 20:28 ` Andy Wingo
2012-01-29 21:14 ` Bruce Korb
2012-01-29 21:32 ` Mark H Weaver [this message]
2012-01-28 22:59 ` Andy Wingo
2012-01-27 6:27 ` Mark H Weaver
2012-01-27 6:19 ` Mark H Weaver
2012-01-27 14:04 ` Bruce Korb
2012-01-27 14:32 ` Mark H Weaver
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=87y5sqjitv.fsf@netris.org \
--to=mhw@netris.org \
--cc=bruce.korb@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).