Re: should free() refer to posix_memalign?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jonny,

On 10/8/21 3:28 PM, Jonny Grant wrote:
I don't like that list.  It is incomplete (the first one that comes to my mind is asprintf(3)).  Either we provide a _complete_ list of functions that can be free(3)d, which I think will be difficult to keep up to date, or we use the same wording as POSIX, and say that it deallocates memory allocated as if by malloc(3).


What are your thoughts?

That sounds reasonable.

"deallocates" sounds better than "frees"

When I was going to fix it, I noticed that we already had that fixed recently:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=cfc381be29fb7b4f642b8b333882f22628112abe>

Kind regards,

Alex

--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux