quiroz@cs.rochester.edu (Cesar Quiroz) (11/17/87)
I regret not having a recent copy of the draft standard, so I have to ask the net to satisfy my curiosity on this. What would be the consequence of *not* supporting benign redefinitions? Would it just be extra warnings in sloppily written code? Or is macro redefinition a terminal error? If this mechanism is introduced only for the sake of avoiding warnings when people include stdio.h 6 times in a row (or when 2 useful headers include types.h, etc...), then the recent discussions seem to support the idea that the mechanism is not paying for its cost. Wouldn't it be better not to burden the implementors with this unsatisfactory kludge and let them issue warnings to their heart's content? -- Cesar Augusto Quiroz Gonzalez Department of Computer Science ...allegra!rochester!quiroz University of Rochester or Rochester, NY 14627 quiroz@cs.rochester.edu