On Wednesday, January 29, 2003, at 03:29 AM, Stephen J. Turnbull wrote:
>>>>> "Andrew" == Andrew Begel
<abegel(a)cs.berkeley.edu> writes:
Andrew> In both 21.5.10 and 21.4.12, MacOSX/Darwin needs to
Andrew> include <string.h> in sysdll.h to get strcpy(). Aside from
Andrew> adding:
It looks to me like the "normal" way to get string.h is to #include
lisp.h immediately after #include config.h.
Ok.
Low-level support that does not interface with Lisp otherwise seems to
#include it directly. (fgrep string.h src/*.[ch] will demonstrate
that this is common.) Therefore I would say that you should include
it directly in modules that #include sysdll.h. I suspect order
doesn't matter. If it is not obvious from your module code that
strcpy is needed, then add a comment.
Why is this sysdll.h-related?
Because sysdll.c includes it, and both dll_function() and
dll_variable() call strcpy(). The #include really only needs to be in
sysdll.c.
-----------
Andrew Begel
Ph.D. Candidate
Computer Science Division
University of California, Berkeley