This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: struct interface
- To: Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>
- Subject: Re: struct interface
- From: Dirk Herrmann <dirk at ida dot ing dot tu-bs dot de>
- Date: Thu, 6 Apr 2000 18:09:47 +0200 (MEST)
- cc: Michael Livshin <cmm at verisity dot com>, clark dot mcgrew at sunysb dot edu, Guile Mailing List <guile at sourceware dot cygnus dot com>
On 6 Apr 2000, Mikael Djurfeldt wrote:
> I don't want to introduce complexity in the user interface. One
> should be able to write things like:
>
> struct foo {
> char c;
> SCM s;
> }
>
> and rely on that this will work whatever architecture you're running
> on.
>
> If we require users to do explicit padding, I think this will become a
> common source of bugs.
Except if we add a debug mode in which at runtime the alignments are
checked with every call to the SCM_MEMORY_WORD macro.
However, my temporary concern is not how to care for extensions to guile
which are in a maybe-not-too-near future. The question is, whether the
suggested macros make sense and whether we should try to direct the
majority of guile's current memory accesses through such a set of
macros. Is this, for example, something helpful for the introduction of
the new garbage collection mechanisms?
Best regards
Dirk Herrmann