[2060] in Kerberos_V5_Development
Re: malloc.h is not standard
daemon@ATHENA.MIT.EDU (Tom Yu)
Mon Dec 2 21:17:16 1996
Date: Mon, 2 Dec 1996 21:17:04 -0500
To: Ezra Peisach <epeisach@MIT.EDU>
Cc: Paul A Vixie <paul@vix.com>, krbdev@MIT.EDU
From: Tom Yu <tlyu@MIT.EDU>
In-Reply-To: <9612030208.AA20469@kangaroo.mit.edu>
A quick check reveals:
./kadmin/testing/util/tcl_kadm5.c:#include <malloc.h>
./kadmin/testing/util/tcl_ovsec_kadm.c:#include <malloc.h>
./lib/gssapi/mechglue/mglueP.h:#include <malloc.h>
./lib/krb4/memcache.c:#include <malloc.h> /* REQUIRED for near/far declarations */
./util/dyn/dynP.h:#include <malloc.h>
./util/dyn/test.c:#include <malloc.h>
./windows/cns/cns.c:#include <malloc.h>
./windows/cns/tktlist.c:#include <malloc.h>
./windows/wintel/k5stream.c:#include <malloc.h>
We're not using the gssapi/mechglue stuff, so that shouldn't matter
too much. We are compiling the kadmin/testing stuff always, whether
or not they will actually run. util/dyn usages of malloc.h may be
ifdef'ed around, so we may not consider this a problem.
Do we really think the malloc.h issue merits a code thaw?
---Tom
