From: Ken Raeburn <raeburn@raeburn.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: more compilation failures: -DSCM_DEBUG_TYPING_STRICTNESS=2
Date: Tue, 1 Sep 2009 18:29:42 -0400 [thread overview]
Message-ID: <AB2B1811-03FE-44DC-8645-7CA0DC103A72@raeburn.org> (raw)
In-Reply-To: <87bplu4fbr.fsf@gnu.org>
On Sep 1, 2009, at 15:47, Ludovic Courtès wrote:
>> Compiling with SCM_DEBUG_TYPING_STRICTNESS=2 as discussed in __scm.h
>
> Another compilation flag that must be rarely used. :-)
>
> Do you find it useful?
Not so far. :-) There seems to be a lot of otherwise correct code
making assumptions about using casts or "==" or whatever; I haven't
sorted out whether there are actual bugs being flagged in there too.
The corresponding code in Emacs has helped me track down code that was
being sloppy about mixing integers and Lisp values, and that was good,
since I'm trying to change things so that integers represented in Lisp
have bit patterns different from the integers themselves, so you
really need to make the distinction. But IIRC it took a while to make
it work again, because nothing was really using it when I started
poking at it.
In the Guile case, I'm a tiny bit concerned about some of the pointer/
int games played (e.g., I'm pretty sure C99 does not guarantee that
you can convert an arbitrary uintptr_t value to pointer and back and
be guaranteed of getting the original value... but I don't know of a
platform that actually violates that assumption), but only a tiny bit.
> My preference is for #2 because: (1) I've never used it ;-), and
> (2) we're moving away from C anyway. Hmm, weak arguments maybe.
>
> Anyway, in the meantime, we can conditionalize static initialization
> stuff from bdw-gc-static-alloc on STRICTNESS == 0 and keep everyone
> happy.
>
> Does that sound reasonable?
Sure. Actually, STRICTNESS=1 is the default -- 0 makes SCM an
integer, 1 makes it a pointer to a struct, which adds a little more
type safety, and 2 makes it a union, which breaks casting,
initialization, etc.
>> It looks like the eval code is going to be annoying too
>
> I wouldn't worry much about this one either as its probably doomed,
> once
> Andy's eval cleanup work is mature.
>
> Things have been moving too fast lately!
I'm not going to complain about that! :-)
Ken
next prev parent reply other threads:[~2009-09-01 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 6:23 more compilation failures: -DSCM_DEBUG_TYPING_STRICTNESS=2 Ken Raeburn
2009-09-01 6:26 ` Ken Raeburn
2009-09-16 19:20 ` Andy Wingo
2009-11-18 5:52 ` Ken Raeburn
2009-11-18 9:37 ` Ludovic Courtès
2009-11-18 20:40 ` Ken Raeburn
2009-11-18 21:18 ` Andy Wingo
2009-11-18 23:09 ` Ludovic Courtès
2009-09-01 19:47 ` Ludovic Courtès
2009-09-01 22:29 ` Ken Raeburn [this message]
2009-09-02 8:08 ` Ludovic Courtès
2009-09-02 18:17 ` Ken Raeburn
2009-09-03 11:48 ` Ludovic Courtès
2009-09-08 23:37 ` Neil Jerram
2009-09-09 1:41 ` Ken Raeburn
-- strict thread matches above, loose matches on Subject: below --
2009-09-01 4:52 Ken Raeburn
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=AB2B1811-03FE-44DC-8645-7CA0DC103A72@raeburn.org \
--to=raeburn@raeburn.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).