Re: Better support for transition to guile-1.6

[Marius Vollmer]

Mikael Djurfeldt <address@hidden> writes:

> 2. Many application developers will want not just to upgrade to
>    guile-1.6 but *maintain backward compatibility* with older Guile
>    releases.

Doesn't the deprecation mechanism now in place help with this?  The
way I imagined the switch to happen was that people that wanted to
stay compatible with 1.4 would compile Guile with --enable-deprecated
and _not_ switch to the new stuff of 1.6.  For example, your compat.h
excerpt is the reverse of what we have in libguile.h.  There we define
the old type names in terms of the new ones and people can continue to
use the old names until 1.8 comes out.  To check whether they are
ready for 1.8 they can compile Guile with --disable-deprecated (or
install a 1.7 snapshot).

More support for the switch is certainly good, I'm just trying to
understand whether we are about to fork strategies here.