Colin Watson <[email protected]> writes: > (Incidentally I don't understand how the description of when the > difference matters matches up with it being deprecated, but maybe I > just don't understand Heimdal well enough.)
The description of when the difference matters is, I believe, actually the description of why the free function exists at all instead of calling free(). Since the return value is a simple char *, the obvious thing to do would be for the caller to just call free(). This isn't done because, on Windows, the free() has to be done by the same object that did the memory allocation, so you need a library API for the free. I don't think that comment was intended to have anything to do with the difference between krb5_free_unparsed_name and krb5_xfree. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
