> Especially when you consider code generation. That's a very good point you are making here. However, as I said elsewhere, I don't see the use of being able

> Especially when you consider code generation. That's a very good point you are making here. However, as I said elsewhere, I don't see the use of being able to either write typedef int ... or int typedef ... and I don't think that proper code generation would require it.