Robert Shearman <[EMAIL PROTECTED]> writes: > I disagree. The global make rules, among other things, should enforce > policies whether this be telling the C compiler to error on certain > non-portable constructs like declarations after statements or telling > flex not to output code that includes headers that might not be > present, like unistd.h.
Yes, but policies about headers don't always apply globally. Some parts of the project, like the server, are Unix-only, and using unistd.h in those parts is perfectly legitimate. -- Alexandre Julliard [EMAIL PROTECTED]
