On Wed, May 28, 2014 at 11:18:14AM +0200, Kristian Lein-Mathisen wrote:
I realize I already put down my vote, but I'd like to promote my case after
some thought. I guess what we're trying to find out is what's more
troublesome and/or surprising:
1. having to set the port explicitly (to #f?)
On Mon, Jun 02, 2014 at 05:35:01PM +0200, Peter Bex wrote:
Dear CHICKEN users,
We are pleased to announce the immediate availability of CHICKEN 4.9.0
at the following URL:
http://code.call-cc.org/releases/4.9.0/chicken-4.9.0.tar.gz
Dear CHICKEN users,
It has been pointed out that 4.9.0
On Sat, Jun 07, 2014 at 04:06:51PM +0200, Peter Bex wrote:
The tarball is available in the usual location:
http://code.call-cc.org/releases/4.9.0.1/chicken-4.9.0.1.tar.gz
Of course that URL should be
http://code.call-cc.org/releases/4.9.0/chicken-4.9.0.1.tar.gz
Kind regards,
The CHICKEN Team
Peter Bex scripsit:
c) The port should not be reset, but the uri should be printed without
port if it's the default for this scheme.
+1 for (c).
--
John Cowan http://www.ccil.org/~cowanco...@ccil.org
Is a chair finely made tragic or comic? Is the portrait of Mona Lisa
