From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: proposal: stricter type-checking for macros
Date: Sun, 25 Apr 2004 00:09:51 +0200 [thread overview]
Message-ID: <87vfjpdo40.fsf@zagadka.ping.de> (raw)
In-Reply-To: <16482.64542.175708.694774@localhost.localdomain> (Han-Wen Nienhuys's message of "Thu, 25 Mar 2004 16:34:54 +0100")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> I vote for
>
> #define TYPECHECKED(x) (0? (*(SCM*)0=(x)): x)
>
> which returns x, and obviates the void casting.
How would you want to install this into Guile? Would it be part of
the public API or would we just use it in a lot of places ourselves?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-04-24 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 12:23 proposal: stricter type-checking for macros Han-Wen Nienhuys
2004-03-25 15:27 ` Paul Jarc
2004-03-25 15:34 ` Han-Wen Nienhuys
2004-04-24 22:09 ` Marius Vollmer [this message]
2004-04-24 22:54 ` Han-Wen Nienhuys
2004-04-24 23:42 ` Marius Vollmer
2004-03-31 23:08 ` Paul Jarc
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=87vfjpdo40.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).