[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] [PATCH] Raise error on construction of too large v
From: |
Felix |
Subject: |
Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs |
Date: |
Mon, 05 Mar 2012 13:53:09 +0100 (CET) |
From: Christian Kellermann <address@hidden>
Subject: Re: [Chicken-hackers] [PATCH] Raise error on construction of too large
vectors/blobs
Date: Mon, 5 Mar 2012 13:47:32 +0100
> * felix winkelmann <address@hidden> [120305 13:41]:
>> Hi!
>>
>> I wonder if it is a good idea to test vector limits by allocating a
>> vector of #x100000000000000 elements.
>
> The rationale behind this is:
>
> It should not allocate anything but raise an error. If it does it
> will exhaust memory and that is also an error, resulting in a panic.
>
> Does that make sense? I just want to make sure that the error is caught...
> Maybe there is a better way?
Ah, you check for an error. An oversight on my part. Well, you could try
negative lengths and so on.
Anyway, nevermind.
cheers,
felix
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, (continued)
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, John Cowan, 2012/03/04
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, Felix, 2012/03/05
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, Christian Kellermann, 2012/03/05
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs,
Felix <=
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, Christian Kellermann, 2012/03/05
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, Christian Kellermann, 2012/03/05
- Re: [Chicken-hackers] [PATCH] Raise error on construction of too large vectors/blobs, Christian Kellermann, 2012/03/11