The point is to visually distinguish the function from free(). After all, if the user uses H5free_memory() to free a buffer they allocated, then they have the original problem, only reversed :)
The longer function name indicates that it is special and has a particular use. Dana > -----Original Message----- > From: Hdf-forum [mailto:[email protected]] On Behalf > Of Rhys Ulerich > Sent: Tuesday, March 25, 2014 9:10 AM > To: HDF Users Discussion List > Subject: Re: [Hdf-forum] [Re] RFC: Freeing Memory Allocated by the HDF > Library > > > Why H5free_memory and not just H5free? ;-) > > If I saw "H5free" in an API, I'd start looking for "H5malloc". > > Similarly, if I saw "H5free_memory" I'd think someone didn't know C custom is > to use "free". > > H5free_buffers gives some indication that they're long-lived storage locations > and likely not to be mucked with casually. > > - Rhys > > _______________________________________________ > Hdf-forum is for HDF software users discussion. > [email protected] > http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
