closure api return value types problem

[Wayne Meissner]

On 8 April 2010 17:25, Andrew Haley <aph@redhat.com> wrote:

> There's nothing slight about this API change, though.  I think it
> would break all clients of the closure interface, and wouldn't it mean
> changing all the back-ends too?  Perhaps it would make sense to add a
> new API with the desired behaviour.  Sometimes, even though a decision
> may have been wrong, it makes more sense to keep it than to
> retroactively make a change.
>

Agreed.  Absolutely needs a new api for this, if the change goes
ahead.  Otherwise, too much software would compile correctly, but
implode when used, and I for one don't want that pain.

I think in this particular case, just good documentation on the quirk
would be sufficient.  I know I've hit it before, but just looked at
the test suite and thought "that must be the way to do it", fixed
things up, and moved on.