From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Goops & Valgrind
Date: Fri, 22 Aug 2008 21:00:11 +0200 [thread overview]
Message-ID: <87fxowdgec.fsf@gnu.org> (raw)
In-Reply-To: m3zlnaup4c.fsf@pobox.com
Hello,
Andy Wingo <wingo@pobox.com> writes:
> There could be two fixes. One would be to assume that the Scheme code
> that calls %fast-slot-ref et al is well-formed, and thus we need no
> bounds checking. It's all in goops.scm, so this would be a decent
> assumption. The other would be to use a different definition of
> SCM_NUMBER_OF SLOTS, which would probably have a different purpose:
>
> #define SCM_NUMBER_OF_FIELDS(x) (SCM_STRUCT_VTABLE (x)[scm_si_nfields])
I'm not sure I understand all the details right now, but I would welcome
patches. :-)
That said, AFAIK, primitives always do as much run-time checking as
needed, making no assumption about the correctness of Scheme code. I
think it would be nice to follow that philosophy, unless it yields a
performance hit.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-08-22 19:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 5:15 Goops & Valgrind Han-Wen Nienhuys
2008-08-18 15:50 ` Ludovic Courtès
2008-08-19 8:58 ` Han-Wen Nienhuys
2008-08-18 18:58 ` Andy Wingo
2008-08-22 19:00 ` Ludovic Courtès [this message]
2008-09-11 21:06 ` Neil Jerram
2008-09-12 19:22 ` Andy Wingo
2008-09-14 12:06 ` Neil Jerram
2008-09-14 17:03 ` Neil Jerram
2009-01-04 12:29 ` Andy Wingo
2009-01-04 21:01 ` Neil Jerram
2009-01-04 23:36 ` Neil Jerram
2008-09-16 7:25 ` Mikael Djurfeldt
2008-09-16 9:29 ` Neil Jerram
2008-08-19 11:53 ` Mikael Djurfeldt
2008-08-19 15:19 ` Han-Wen Nienhuys
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=87fxowdgec.fsf@gnu.org \
--to=ludo@gnu.org \
--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).