Date: Fri, 21 Aug 1998 17:58:55 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: Don.Lewis@tsc.tdk.com Cc: hackers@FreeBSD.ORG Subject: Re: Realloc fix for review Message-ID: <199808212258.RAA00602@detlev.UUCP> In-Reply-To: <199808210523.WAA08503@salsa.gv.tsc.tdk.com> (message from Don Lewis on Thu, 20 Aug 1998 22:23:43 -0700) References: <199808210523.WAA08503@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> } So rather than hack some really complicated a and na's, I write a new > } function, added it to libc and then modified all of src/lib to use > } this new function. I called it frealloc (freeing realloc). I added > } it to the man page, etc. I know that this isn't in ANSI C nor in > } POSIX, but after seeing how hard it was to get people to use strncpy > } right, I thought it would be good to add this to libc. > I'd worry about causing name space pollution. You might break someone > else's code who has their own function called frealloc ... Isn't that what weak symbols in libc are for? Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808212258.RAA00602>