🚀 go-pugleaf

fr> Von : fred@cv.ruu.nl (Di, 19.05.92 09:59)
fr> Name: Fred Appelman
fr> Box : University of Utrecht, 3D Computer Vision Research Group
fr> MId : <1992May19.085902.23343@cv.ruu.nl>
fr> RId : <1992May18.132905.20357@crd.ge.com>

fr>> |> 1. This change in the compiler will make your software less portable. I
fr>> How so? What strictly conforming program would break??
fr>
fr> For example:   cout << __NAME__ would break.

"cout << __NAME__" wouldn't be in a strictly conforming program. Or to put it
another way, it would make a program not strictly conforming.

fr> Give an example of this. The extensions are in the library. Not in the
fr> language defintion.

assembler inlines, for example ...

fr> The idea aoub the -ansi flag is that given that a program compiles without
fr> errors, it is compilable with EVERY *ANSI* compiler. This is definitly not
fr> the case.

So what? Turn off __NAME__ iff -ansi. Or better, wait for -ansi -pedantic.

MfG Kai