🚀 go-pugleaf

This message comments on GNU indent 1.5 installation, compiled with
GNU C 1.40 under COFF-encapsulation on a 386/ix 2.0.2 system (waiting
for Hurd to be ready :-).

* The installation improved a lot since GNU ident 1.4; however,
departures from GNU standards, willingful or not, are not necessarily
improvements.  zmakefile.in should still be named Makefile.in and
there should not be a Makefile on the bare distribution.  We are
getting used to call `configure' on all GNU products, there is no real
reason this should be automatic only for GNU indent.  Moreover, as of
now, many goals from zmakefile are not attainable from Makefile (like
`install:' for example), I do not see many good reasons to duplicate
all goals from zmakefile into Makefile just to avoid asking the user
to call configure.  Let's keep all of this simple, and uniform.
Passing by, CONF-README could well be called INSTALL; I know this is
not really part of GNU standards, but this convention is fairly usual.

* The man page is not installed.  It might be on purpose, because of
its unsupported status.  Even then, it would be nice to install it.

* Just `make'ing indent yields:

   io.c:389: parse error before `int'
   io.c:417: parse error before `int'
   io.c:522: parse error before `void'
   io.c:649: parse error before `int'
   io.c:695: parse error before `int'

This is because CC is predefined to be `gcc -ansi -Di386', here.  The
problem comes from the fact that, in sys.h, we read:

   #ifdef __STDC__
   #define INLINE inline
   #else
   #define INLINE
   #endif

But in fact, so far that I know, `inline' is not part of ANSI C.  This
should rather be written:

   #ifdef __GNUC__
   #define INLINE __inline__
   #else
   #define INLINE
   #endif

so it would continue to work even if one uses `gcc -ansi'.

* Many thanks for your continuing support of GNU indent.  This is an
important tool in my library!

-- 
Franc,ois Pinard        ``Vivement GNU!''        pinard@iro.umontreal.ca
(514) 588-4656                                    ...!uunet!iros1!pinard
Consider joining the League for Programming Freedom.  Email for details!