Featured wanted

[Mark Stankus]

Hi,

  There are books which describe things that should or should not be 
done. Part of this has been built into g++. For example,

  if((i=0)) { }

has no warning while

  if(i=0) {}

does give a warning.

  WHAT I WANT is a feature so that g++ "tells you about your code".
This would include, for example, text on the screen which
described the introduction of temporaries (and where the
"explicit" keyword would make a difference for the use
of a constructor). For example,

  long int i = 0;
  while(i!=0) {
    //whatever
  }

is less efficient than

  long int i = 0L;
  while(i!=0L) {
    // whatever
  }

  I KNOW that some of you will say that this does not belong in a 
compiler. Fine... how about building an application which does the
front end analysis which uses alot of gcc code? Or you might say
that a programmer should be smarter than to make such a mistake.
That is stupid and arrogant. Especially if you are looking at
alot of other people's code and are curious whether it is inefficient
for some reason (such as lots of temporaries).

  The output can be very verbose. Ideally it would be set up so that
it could be used efficiently along with fgrep.

Mark Stankus