[racket-dev] Removing Xexpr preference from Web Server

On Tue, Nov 30, 2010 at 5:18 AM, Eli Barzilay <eli at barzilay.org> wrote:
> Yesterday, Robby Findler wrote:
>> This kind of thing has happened many times for other parts of the
>> system (the class system is a good example). We have generally tried
>> to avoid so much breakage and I think we should here. One technique
>> is to have a new name for the new version (or a new name for the old
>> one if that is more appropriate; that still breaks everything but
>> porting is very easy).
>
> The problem here is that there is no name to change -- it's the
> implicit "coercion" of xexpr values to a response.

Why can't there be two libraries, one that coerces and one that
doesn't? More generally, one that acts the same as the current library
and one that is intended for new code?

Robby