From: dsmith@actron.com (Dale P. Smith)
Cc: hanwen@xs4all.nl, guile-devel@gnu.org
Subject: Re: typechecking
Date: Mon, 10 May 2004 17:47:41 -0400 [thread overview]
Message-ID: <87k6zkj6o2.fsf@actron.com> (raw)
In-Reply-To: <87brkwc6f7.fsf@zagadka.ping.de> (Marius Vollmer's message of "Mon, 10 May 2004 23:34:52 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>> I propose that the old
>>
>> DEBUG_TYPING_STRICTNESS==2
>>
>> is removed, as it provides little extra strictness.
>
> Hmm, I don't agree. That setting is much stricter than the default
> one: Guile itself has many places that would need to be fixed for
> STRICTNESS == 2. For example, code like
>
> SCM x;
>
> if (x == SCM_EOL)
> ...
>
> does not compile with STRICTNESS == 2, and it is indeed not completely
> correct. (It should be SCM_EQ_P (x, SCM_EOL) or SCM_NULLP (x).)
>
> It would be a nice little (?) project to make Guile compile with
> STRICTNESS == 2. Some places, like
>
> switch (ISYMNUM (SCM_CAR (x)))
> {
> case (ISYMNUM (SCM_IM_AND)):
>
> in eval.c might be hard to fix, tho.
I thought that STRICTNESS == 2 was for extreme type checking, but for
suboptimal code, and that Guile code should always be able to be
compiled at level 2.
-Dale
--
Dale P. Smith
dsmith at actron dot com
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-05-10 21:47 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 ` Dale P. Smith [this message]
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 ` 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=87k6zkj6o2.fsf@actron.com \
--to=dsmith@actron.com \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).