"Magnus Hagander" <[EMAIL PROTECTED]> writes: >> which looks like they figured out that they needed to check >> for MicroSoft C explicitly. I have no idea why they do not >> define __STDC__ however.
> Can we just define __STDC__ when compiling that file (or rather, when > compiling any bison-generated output file)? Or is that likely to cause > *other* issues? That seems pretty risky. Better to use the /Za switch or whatever it was to get the compiler to assert it for itself. We have precedent for adding yes-we'd-like-a-standard-compiler-please switches where necessary, for instance adding -Ae to CFLAGS for HP's compiler. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend