[2238] in Kerberos_V5_Development
Re: Memory allocation/freeing
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Wed Feb 19 01:28:43 1997
Date: Wed, 19 Feb 1997 01:28:20 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "Richard Basch" <basch@lehman.com>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, "Richard Basch"
<basch@lehman.com>,
krbdev@MIT.EDU
In-Reply-To: Richard Basch's message of Wed, 19 Feb 1997 01:16:20 -0500,
<199702190616.BAA28773@badger.lehman.com>
Date: Wed, 19 Feb 1997 01:16:20 -0500
From: "Richard Basch" <basch@lehman.com>
Given the routine and how the realloc is done, I sure hope that it is
not generally available to application developers...
If we had an API document, it'd say something about "use this only if
you really know what you are doing it." :-) Actually, as long as you
follow a few simple rules, it's not all that hard.
Anyway, we still
need a routine to free the memory allocated by it. Suggestions?
krb5_free_name(krb5_context, char *) ?
How about
krb5_free_unparsed_name(krb5_context, char *)
- Ted
