unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: typechecking
Date: Thu, 10 Jun 2004 18:22:40 +0200	[thread overview]
Message-ID: <87n03bjsbz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <16569.39703.372961.365613@localhost.localdomain> (Han-Wen Nienhuys's message of "Sun, 30 May 2004 10:28:07 +0200")

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

> dirk@dirk-herrmanns-seiten.de writes:
>> >>    
>> >>
>> >
>> >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?
>> >
>> SCM values, where the 3 least significant bits are zero indicate 
>> non-immediates. That is, the SCM value can without any modification be 
>
> I understand the tag system, so I'm aware of the
> implications. However, I was wondering whether such a change stands a
> chance of being incorporated, if it would work.

I find it quite tempting to make SCM_BOOL_F identical to 0; it will
prevent a lot of bugs.  But I do think it is better to not gurantee
anything like this about the SCM type (except that you can assign it
directly).

A properly abstract interface to SCM values is a good thing, even if
it is inconvenient at times.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2004-06-10 16:22 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             ` Marius Vollmer [this message]
2004-05-30 14:00         ` typechecking Andy Wingo

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=87n03bjsbz.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).