Re: realloc() - frequency, conditions, or experiences about relocation?

On 24/06/2024 22:28, Keith Thompson wrote:

scott@slp53.sl.home (Scott Lurndal) writes:

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

[...]

Baby X has bbx_malloc() which is guaranteed never to return NULL, and
never to return a pointer to an allocation which cannot be indexed by an
int.

>
What do you mean by 'indexed by an int'?  So, what happens if I index
your allocation with -109235?
>
Or did you mean to say unsigned (or positive) int less than the
size of the allocation?

 If I recall correctly, Malcolm hates size_t.  I presume that
bbx_malloc() will never allocate more than INT_MAX bytes.
 

Exactly.
Currently bbx_malloc() does take a size_t, but there version in which it takes an int. However you get warning sif yiub try something like bbx_mallcc(10 * sizeof(int)) on the basis that expressin is size_t.
But if you pass either a negative number or more than iNT_MAX, it assumes the request is invalid and terminates with an error message.
--
Check out my hobby project.
http://malcolmmclean.github.io/babyxrc