guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Portability problem with SCM_DEBUG_TYPING_STRICTNESS=1


From: Dirk Herrmann
Subject: Re: Portability problem with SCM_DEBUG_TYPING_STRICTNESS=1
Date: Thu, 7 Jun 2001 15:50:56 +0200 (MEST)

On 7 Jun 2001, Matthias Koeppe wrote:

> The setting SCM_DEBUG_TYPING_STRICTNESS=1, which has been made the
> default recently, reveals portability problems in the Guile sources:
> The Sun Forte compilers report "a cast does not yield an lvalue" in a
> few places in the Guile sources, for instance in goops.c where
> assignments to an application of the SCM_SLOT macro are done like
> this:
> 
>         SCM_SLOT(z, scm_si_name) = name;
> 
> (where SCM_SLOT reduces to SCM_PACK)
> 
> I'd suggest that constructions like this be avoided.  Macros like
> SCM_SET_SLOT should be introduced and used instead. 
> 
> Other places are weaks.c (scm_make_weak_key_hash_table,
> scm_make_weak_value_hash_table, scm_make_doubly_weak_hash_table) and the
> SCM_BITVEC_SET, SCM_BITVEC_CLR macros used in ramap.c and unif.c. 

Thanks for the bug report.  However, since I don't have access to the
compiler you mention and since on my machine no errors are reported, it
would be nice if you could send us the full set of error
messages.  Sending a patch would be even nicer :-)

Best regards,
Dirk Herrmann




reply via email to

[Prev in Thread] Current Thread [Next in Thread]