Yannick Duch�ne (Hibou57) wrote:
> Le Thu, 17 Feb 2011 12:04:00 +0100, J-P. Rosen <rosen@adalog.fr> a
> écrit:
>> Le 17/02/2011 00:35, Peter C. Chapin a écrit :
>>> A macro defined in someheader.h might change the meaning of the
>>> declarations in someotherheader.h.
>> And especially the following one:
>> #define private public
>>
>> Great for those who think that information hiding is a nuisance!
>
> I am not joking here : at the time I learned C/C++, I hired a book
> from a library,

Seriously dude, you don't "hire" a book from a library unless you are way 
stupid (no offense, you are not my problem).

> which was proudly stating C/C++ macros are so much
> powerful (sic) that one may "#define BEGIN {", "#define END }" and so
> on, so as to happily write BASIC in C/C++ ! And that was not a book
> playing the fool on C/C++, that book was promoting C/C++.

I use that mechanism for "templates". It may not be scalable, but I don't 
need a driver's license to drive. AGE CHECK!