Re: When to check the return value of malloc
- From: Ulrich Eckhardt <doomster@xxxxxxxx>
- Date: Fri, 25 Jan 2008 18:26:49 +0100
Richard Tobin wrote:
In article <5vtdu2F1nf6g1U1@xxxxxxxxxxxxxxxxx>,
Ulrich Eckhardt <doomster@xxxxxxxx> wrote:
I'm certainly not suggesting that you should use int for a
general-purpose malloc() replacement. Rather, it would be an
argument for size_t being signed.
If it was 32 bits large, why wouldn't I be allowed to allocate 3GiB?
The existence of arguments one way doesn't preclude the existence of
arguments the other way.
Ahem, Richard, in case you were trying to say anything it totally missed me.
Please be a bit more explicit.
Thanks
Uli
.
- References:
- When to check the return value of malloc
- From: Marty James
- Re: When to check the return value of malloc
- From: Ulrich Eckhardt
- Re: When to check the return value of malloc
- From: Richard Tobin
- Re: When to check the return value of malloc
- From: Ulrich Eckhardt
- Re: When to check the return value of malloc
- From: Richard Tobin
- When to check the return value of malloc
- Prev by Date: Re: Is Chris Hills a god?
- Next by Date: Re: Is Chris Hills a troll?
- Previous by thread: Re: When to check the return value of malloc
- Next by thread: Re: When to check the return value of malloc
- Index(es):
Relevant Pages
|