Editing Talk:Main Page/suggestions (section)

== update malloc page according recent C23 changes ==

> Return value
On success, returns the pointer to the beginning of newly allocated memory. To avoid a memory leak, the returned pointer must be deallocated with free() or realloc().


Since C23, realloc cannot be used to free() memory -- zero size for realloc() is undefined behaviour
https://en.cppreference.com/w/c/memory/realloc
: Use of non-zero sized {{tt|realloc}} on the returned pointer does (temporarily at least) address the issue of not leaking memory (either the pointer is deallocated because the memory is newly allocated, or the memory is given "new life" if its region is merely grown). Quite a wordy thing to try and express that, but I do believe that the original intent of that note was not referring to zero-sized {{tt|realloc}}. --[[User:Ybab321|Ybab321]] ([[User talk:Ybab321|talk]]) 05:14, 28 March 2024 (PDT)
:: One possibility that might not be too wordy would be to change sentences like "must be deallocated with free() or realloc()" to "must be deallocated with free() or resized with realloc()". There are a few places where that would have to be done. IMO, it's fine as it is though, especially on the realloc page since that states the behaviour. - Bryce [[Special:Contributions/64.124.34.109|64.124.34.109]] 12:02, 3 April 2024 (PDT)