On Sun, Mar 24, 2013 at 04:32:56PM -0400, Andrei Barbu wrote:
> Hi,
>
> I've attached a patch that allows for initial large heaps given that
> heap is now a size_t.
>
> The original patch did not update CHICKEN_initialize to have a size_t heap.
I'm not sure this can "just" be done or requires a
Jörg F. Wittenberger writes:
> [1. text/plain]
>
> On Mar 25 2013, Moritz Heidkamp wrote:
>
>>Jörg F. Wittenberger writes:
>>> Though in a way the explanation is correct. -strict-types assumes
>>> '() to be null from the initialization. Short of a way to declare
>>> the type of foobar as (list
On Mar 25 2013, Moritz Heidkamp wrote:
Jörg F. Wittenberger writes:
Though in a way the explanation is correct. -strict-types assumes
'() to be null from the initialization. Short of a way to declare
the type of foobar as (list-of ) this fails when it's used
as the initial and correct value
On Mon, Mar 25, 2013 at 09:58:32AM +0100, Jörg F. Wittenberger wrote:
> Though in a way the explanation is correct. -strict-types assumes
> '() to be null from the initialization. Short of a way to declare
> the type of foobar as (list-of ) this fails when it's used
> as the initial and correct v
Jörg F. Wittenberger writes:
> Though in a way the explanation is correct. -strict-types assumes
> '() to be null from the initialization. Short of a way to declare
> the type of foobar as (list-of ) this fails when it's used
> as the initial and correct value of type (list-of ) with
> zero leng
On Mar 24 2013, Moritz Heidkamp wrote:
Peter Bex writes:
As I understand it, strict-types declares variables to never change
their types. So once it's looked at the initial declaration of the
variable, it assigns it a type of null, and then it can never change.
-strict-types assume varia
