Re: malloc()/realloc() - have I got this right?

Antoninus Twink wrote:
On 30 May 2008 at 21:53, CBFalconer wrote:
Ridiculous. Most use of the function simply runs until a non-zero
is returned, after which the operation ends. It may be because of
EOF, or because of error. In either case, no further input is
available.

If you're in a restaurant and can't get your meal either because
they've run out of salmon or because the kitchen's on fire, you might
find it useful to be able to distinguish between those two error
conditions.
For some reason that is beound me you elected to ignore CBF's next sentence,
which addresses exaclty that:
If there is a need to distinguish EOF from errors, it
can be done at that point.
In you analogy: just ask the waiter for the reason or listen to the fire
alarm.

Bye, Jojo



.