> > BROKEN: a is 'my_type', not 'int ' > > The C programmer here has explicitly defined my_type to be > the same as int. > If the programmer becomes confused, it is his own fault. > > On the other hand, the Perl programmer has not explicitly > defined string > interpolation to be the same as string concatenation. That is an > implementation detail of the Perl compiler. The programmer > should not be > required to know the internals of the compiler. wchar_t in MSVC++ is typedef'd somewhere in it's internal headers and programmer not only does not care it's real type, but he(she) should not rely on it's real type, because it may change. But compiler gives warnings about "unsigned short int" (AFAIR). Here are internals of compiler. I think many more examples may be given, example about typedef just came to me because I saw it today... Good luck, Vadim.Thread Previous | Thread Next