Re: Eval options macro: backward compatibility?

[Kevin Ryde]

Han-Wen Nienhuys <address@hidden> writes:
>
> what is the status of the eval options structure wrt binary compatibility?

I remeber now: changing the size of a data object in a shared library
breaks mainlines using it, or even just taking its address.  And both
mainline and the library are broken, since the object is truncated to
the smaller size for both.  This is a bit subtle, but it bit for
instance in some of the old Xaw replacement libraries in the past.

If you think noone is using it then rename to scm_i_.  Or if you think
it's used then growing breaks it so take the opportunity to change to
a pointer at the same time.