On 01/19/2011 02:20 PM, Tom Lane wrote: > fche@xxxxxxxxxx (Frank Ch. Eigler) writes: >> I agree. It's not a great situation, but local GCC/C++ experts have >> found no better way to type-analyze the parameters, to ensure their >> safe passage to the tool. (Our testing shows <limits> is not >> offensive to other C++ apps we've seen.) > > What I was more worried about was what happens when sdt.h is included in > plain C code. Whatever you think of C++ apps that don't play nice with > <limits>, such a complaint is unlikely to impress authors of plain C > apps. That bit is only present within "#ifdef __cplusplus". The "#else" part for C uses a different trick including __builtin_choose_expr(). Josh -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
