From: Andy Wingo <wingo@pobox.com>
Subject: Re: typechecking
Date: Sun, 30 May 2004 15:00:21 +0100 [thread overview]
Message-ID: <1085925620.23380.77.camel@localhost> (raw)
In-Reply-To: <16564.54949.13882.819772@localhost.localdomain>
On Wed, 2004-05-26 at 19:40 +0200, Han-Wen Nienhuys wrote:
> It would be interesting to see if we could map the Scheme semantics
> (true = !SCM_BOOL_F) to C. That would require mapping SCM_BOOL_F to
> (void*)0x0. Is this desirable, and does anyone see a possibility for this?
I've been caught by this error a few times, and the scheme true/false
semantics do map nicely to C.
Howeverm the idea has some problems. For one, I don't think passing a
union to `if' (which is what SCM is in SCM_DEBUG_TYPING_STRICTNESS==2)
works.
Secondly, I might be bit-stupid, but after about five minutes of
looking, I can't find a nice set of tc3 type tags having #f==0 for which
a fast SCM_IMP can be defined. This hints that trying to do #f==0 is a
bad idea because it constrains the implementation.
Dunno, just my cent-and-a-half.
--
Andy Wingo <wingo@pobox.com>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-05-30 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 13:04 typechecking Han-Wen Nienhuys
2004-05-10 21:34 ` typechecking Marius Vollmer
2004-05-10 21:47 ` typechecking Dale P. Smith
2004-06-10 16:16 ` typechecking Marius Vollmer
2004-05-10 22:57 ` typechecking Han-Wen Nienhuys
2004-05-15 9:16 ` typechecking Dirk Herrmann
2004-05-16 15:11 ` typechecking Han-Wen Nienhuys
2004-05-17 18:31 ` typechecking Marius Vollmer
2004-05-26 17:40 ` typechecking Han-Wen Nienhuys
2004-05-30 8:40 ` typechecking Dirk Herrmann
2004-05-30 8:28 ` typechecking Han-Wen Nienhuys
2004-05-31 7:05 ` typechecking Dirk Herrmann
2004-06-10 16:22 ` typechecking Marius Vollmer
2004-05-30 14:00 ` Andy Wingo [this message]
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=1085925620.23380.77.camel@localhost \
--to=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).