On 27 May 2007, Han-Wen Nienhuys said: > Johannes Schindelin escreveu: > >>> ((Tcl_Obj **) objv) += (async + 3); >> >> Ah yes, I was using MinGW's own GCC, which is GCC 3.something. >> >> It is a new "feature" of GCC 4.x to disallow constructs like these. >> (Probably because GCC people think that other people are not intelligent >> enough to understand such constructs, and therefore prohibit their use.) > > I very much doubt that. GCC uses type information to determine whether > pointers might be aliased. I think disallowing such constructs helps with > compiler optimization. Actually it was simply too difficult to maintain this extension over the C and C++ parser rewrites in the early 4.x timeline. (Also, IIRC, it had some *nasty* ambiguities, especially in C++.) -- `On a scale of one to ten of usefulness, BBC BASIC was several points ahead of the competition, scoring a relatively respectable zero.' --- Peter Corlett - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
