🚀 go-pugleaf

kanze@gabi-soft.fr (J. Kanze) writes:
	...
>Fortran basically says that the results are undefined if aliasing is
>present, C/C++ doesn't.  (In this regard, one could very easily argue
>that C/C++ is safer.  In fact *in* *this* *regard*, I think it is, in
>that you get defined results even if the arrays overlap.)

Agreed, from practical experience; this _was_ an occasional cause of
very obscure bugs when we used to code in Fortran, as even very
experienced Fortran practitioners were all but clear on the no-alias
rule of that language... I remember people used to disable optimization
(thus often hiding the alias-related bug) and thought they had just hit
"one more optimizer bug"!-).


>I don't know what the current stand is with regards to the proposed C
>extensions, and their incorporation into C++.  The C standard is part of
>C++ `by reference', but in fact, I think that this is only where there

By _const_ reference, surely?-)


Alex
--
DISCLAIMER: these are TOTALLY personal opinions and viewpoints, NOT connected
in any way with my employer, nor any other organization or individual!
Email: martelli@cadlab.it                            Phone: +39 (51) 597313
CAD.LAB s.p.a., v. Ronzani 7/29, Casalecchio, Italia   Fax: +39 (51) 597120

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]