Re: diffutils 2.8.1 ISO C90 compliance patch

[Paul Edwards]

> >> So, whatever solution
> >> works for this, just use the same solution for #include <sys/types.h>.
> >
> > Well I can translate it into DD:INCLUDE(TYPES) and have a
> > member of the PDS called "TYPES".
> 
> Excellent.  Let's do that, then.

You can say the same about any other non-standard file.  The
program should be written properly in the first place.

> > Why not write the code properly to not use non-standard includes?
> 
> But the code is written properly.  

No it isn't.  It has not been written to cater for non-Posix systems.
There is no reason to make text processing programs require
Posix.  We've got a standard for C for a reason.

> Among other things, <sys/types.h>
> is standard.  It is specified by ISO/IEC 9945.  

Which is the standard for Unix, not C.  C is designed to run
on any platform, not just Unix platforms.  C89 is far more
portable than Posix.

> This international
> standard is much more widely available than the C89 standard is.  You
> can see a copy of its current specification for <sys/types.h> at
> <http://www.opengroup.org/onlinepubs/009695399/basedefs/sys/types.h.html>.
> There is no similar resource for C89.

Yes, it is very unfortunate that the C89 standard is not public
domain.  But you can pick up any book on learning C.
sys/types.h is not there, and nor is it required for text processing
programs.  The code should be written properly.

BFN.  Paul.