Two minutes ago, Neil Van Dyke wrote:
>
> I also think that Eli's option #1 could be done without breaking
> backward-compatibility, but I'm not sure it's worth the effort in
> code and documentation, and I don't want to discourage him moving
> forward with #1 by making the task harder than it has to be.
Heh, I just thought about a way to do that, which is likely what
you're thinking of:
* `net/url-unit' and `net/url-sig' stay the same. Code that uses
them works as before.
* `net/url' becomes the (non-unit, of course) library that does
dispatching over "https" with an ssl connection.
This might work, but would be very odd. Specifically, the description
of `net/url-unit' will need to mumble something about creating a
result that is *not* like `net/url' in that there is no such dispatch.
Backwards compatible, but IMO very ugly. But perhaps it's worth it?
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
