Re: What's wrong with C++?

[richard <catbird.island@gmail.com>]

On Feb 17, 3:52 am, Georg Bauhaus <rm-host.bauh...@maps.futureapps.de>
wrote:
> On2/17/11 12:04 PM, J-P. Rosen wrote:
>
> > 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!
>
> It is good to know that source code transformation
> can change the meaning of source text.  I don't think
> this argument will convince.  Is there substantial evidence
> of programs that #define private to be public? Might be.
> The change is a conventional trick to use with introspective
> languages, and useful.
>
> But anyway, the argument is easily refuted as by
> firing this riposte:
>
> procedure Safe is
>
>      function "+" (Left, Right: Integer) return Integer is
>      begin
>          return 0;
>      end "+";
>
>      A : array (Integer range 1 .. 2) of Integer;
> begin
>      for K in A'Range loop
>          A (A'First + K - 1) := 666;
>      end loop;
> end Safe;
>
> Make "+" a little more obscure (if possible) and have
> a proponent of Ada look for the error...
>
> Or talk about the possibility (or not) of changing the
> definition of Integer temporarily to a debugging version
> of Integer whose operations we can trace.
We do not use predefined type integer in production code.  If you
define your own constrained integer type, this is not likely to be a
problem.