Re: Guile: What's wrong with this?

[Andy Wingo]

On Wed 04 Jan 2012 14:29, Mark H Weaver <address@hidden> writes:

> Although this is a closer emulation of the previous (broken) behavior,
> IMHO this would be less desirable than simply doing (string-copy "foo")
> on every evaluation of "foo", which seems to be what Bruce (and probably
> others) expected "foo" to do.

Thing is, why are we doing this?  We know what the correct behavior is,
as you say:

> Of course, I'm only talking about what I think should be done when the
> compiler option is changed to non-default behavior.  I strongly believe
> that the _default_ behavior should stay as it is now.

The correct behavior is the status quo.  We are considering adding a
hack to produce different behavior for compatibility purposes.  We don't
have to worry about correctness in that case, only compatibility.  IMO
anyway :)

Andy
-- 
http://wingolog.org/