🚀 go-pugleaf

    David Linder writes:

>My point before, about, say, LAPACK++, was that lots of existing code is
>sometimes broken by changes to the ANSI standard(s).  That gcc development
>attempts to keep up with this (rather than allow legacy code to keep on
>being compilable) is in opposition to your blanket statement here

    I agree that C++ should converge to a standard rather than
continuing to support non-standard legacy code.  I would have liked
to use Lapack++ to run further tests on gcc, but I can find something
else to use.  (Lapack++ was unusable for me because it did not 
implement eigenvalues and SVDs).

    I got newmat08 to compile (with and without optimizations) by
removing the -fhandle-exceptions and by disabling the the exception
handling in the include.h file.  So either newmat08 is incompatible
with gcc 2.7.2 exception handling or gcc 2.7.2 exception handling is
broken.  Anyway, exception handling is something that I can live
without for now.  (Has EH been standardized?  If so does gcc 2.7.2
implement ANSI EH?)

Dean