Re: gh_enter reconsidered

[Jim Blandy <jimb@red-bean.com>]

> >> In my humble opinion, guile should attempt to scan as LITTLE of the
> >> stack as possible rather than as MUCH as possible. Just do the job that
> >> has to be done. Make clear to the user that the amount of code they hand
> >> over into guile's care represents the amount of protection they get but
> >> GIVE THE USER THE CHOICE.
> >>
> >
> >Do you mean the user has to explicitly ask for stack protection for
> >ranges he cares about, instead of letting Guile find the top of the
> >stack? To me that sounds too close to going back to the bad old days
> >of having to explicilty protect all values on the stack.
> 
> I think what he means it that the programmer should tell guile where
> the highest point of the stack that he intends to use is. I can
> imagine the situation that you have some huge application and you
> intend to tack guile into some tiny part of it to do some small
> job. Having guile search the entire stack is overkill, not to
> mention increasing the chances of more false pointers leading to
> uncollected garbage.

We've been through this before.  Guile isn't going to do that.  :)

I think it's really bad interface design, and I think we can do
better.