* felix winkelmann [110930 13:06]:
> From: Christian Kellermann
> Subject: Re: [Chicken-hackers] [PATCH] add input- and output port types
> specifiers
> Date: Fri, 30 Sep 2011 12:57:47 +0200
>
> > * felix winkelmann [110930
> > 08:40]:
> >> From: Alan Post
From: Christian Kellermann
Subject: Re: [Chicken-hackers] [PATCH] add input- and output port types
specifiers
Date: Fri, 30 Sep 2011 12:57:47 +0200
> * felix winkelmann [110930 08:40]:
>> From: Alan Post
>> Subject: Re: [Chicken-hackers] [PATCH] add input- and output port types
* felix winkelmann [110930 08:40]:
> From: Alan Post
> Subject: Re: [Chicken-hackers] [PATCH] add input- and output port types
> specifiers
> Date: Thu, 29 Sep 2011 06:21:22 -0600
The following hunk has nothing to do with ports but it is not used so I agree.
> -;;; generate
From: Alan Post
Subject: Re: [Chicken-hackers] [PATCH] add input- and output port types
specifiers
Date: Thu, 29 Sep 2011 06:21:22 -0600
> On Thu, Sep 29, 2011 at 03:46:41AM -0400, Felix wrote:
>> The attached patch introduces separate type-specifiers for input- and
>> output
From: Alan Post
Subject: Re: [Chicken-hackers] [PATCH] add input- and output port types
specifiers
Date: Thu, 29 Sep 2011 06:21:22 -0600
> On Thu, Sep 29, 2011 at 03:46:41AM -0400, Felix wrote:
>> The attached patch introduces separate type-specifiers for input- and
>> output
On Thu, Sep 29, 2011 at 03:46:41AM -0400, Felix wrote:
> The attached patch introduces separate type-specifiers for input- and
> output-ports. The old "port" type is still available but only
> abbreviates "(or input-port output-port)". types.db has been
> changed accordingly and is thus not compati
The attached patch introduces separate type-specifiers for input- and
output-ports. The old "port" type is still available but only
abbreviates "(or input-port output-port)". types.db has been
changed accordingly and is thus not compatible to old chickens
(so needs bootstrap).
cheers,
felix
commi