Re: stumped by scm_car/scm_cdr

[Han-Wen Nienhuys <hanwen@xs4all.nl>]

hanwen@xs4all.nl writes:
> > One more idea: it might be that you (harmlessly) used SCM_CAR or
> > SCM_CDR on a non-pair but scm_car/scm_cdr are now complaining about
> > this by throwing an error.  That error might happen in a context where
> > throwing does not work, or might lead to endless recursion, or some
> > other anomaly.  Try replacing the call to scm_wrong_type_arg_msg in
> > scm_car and scm_cdr with a simple abort.
> 
> I tried to remove all fishy looking places where SCM_C[AD]R were used,
> and now it seems to work OK. You might want to consider just doing
> abort() or a something similar as a standard. If the C code uses the
> API incorrectly, then (IMO) this is not something that should be
> signaled at Scheme level using scm_error(), because no amount of
> Scheme coding can fixup such errors.

for the record, these fishy places were mostly in GC mark functions,
where I did

  smobbed_type * p = (smobbed_type*) SCM_CDR(scm) 

iso.

  smobbed_type * p = (smobbed_type*) SCM_GC_CELL_WORD1(scm) 


-- 

 Han-Wen Nienhuys   |   hanwen@xs4all.nl   |   http://www.xs4all.nl/~hanwen 



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel