🚀 go-pugleaf

> In an environment such as we have with C++, where the compiler will occasion-
> ally be undergoing revs or intermediate patches, I would find it useful if the
> compiler would announce a summary at its completion...

In an environment such as many of us have, I think it would be appreciated
if the compiler would be <very> quiet unless it has something of substance to
say.

In UNIX, this is almost a sacred precept (not that there aren't
blasphemers:-).  I wish it were so in other systems.  That is, if you want
the compiler to tell you about itself (instead of doing its normal job,
which is to compile a program), why not ask it that question?

If YOU, personally, feel a need to be reminded of the current version of
the compiler, fine.  That may very well make sense in your environment, but
can't you achieve it with a shell script to control the compilation and
announce the version at the end?

I'm not just being peevish.  (I AM being peevish, but not JUST so.)  It can
be quite annoying to filter the output of a commonly-used program to get
rid of the stuff that doesn't need to be there.  It is more reasonable to
expect a program to generate just the output that is needed, than to expect
it to do extra work to generate anything that MIGHT be needed and then let
its users do extra work to get rid of the noise they don't need.
-- 
Dick Dunn	{hao,ucbvax,allegra}!nbires!rcd		(303)444-5710 x3086
   ...At last it's the real thing...or close enough to pretend.