[Octave-bug-tracker] [bug #33018] ./configure considered broken

[Jordi Gutiérrez Hermoso]

Follow-up Comment #6, bug #33018 (project octave):

> Is Octave ANSI C++ compliant?

No, because there is no such thing, unless you mean the ancient 1998
standard, which is really ANSI/ISO. The C++ standard is currently
maintained by ISO, not by ANSI. And Octave does indeed stay pretty
close to the ISO standard (which, btw, is getting updated and the
final draft of the C++0x standard just got approved), and g++ does a
very good job of staying up to the date with the latest standard.
Indeed, a newer g++ is much closer to ISO C++ than an older one, by
far. I know of several non-standard things that older g++s accepted
for C++ that they shouldn't have. There is also a lot of C++0x that
I'm eager to use in Octave in order to simplify our code.

> FWIW Octave is the only program I would spend this much effort on.
> Anything else would have gotten an "rm -rf" after 2-3 hours unless a
> client was paying me to build it. Particularly w/ the large number
> of compiler warnings being generated.

I hate to say it, but your tone is quite aggressive, and yet you're
asking us to help you. These two attitudes are contradictory. I
recommend you either reconsider your tone or you reconsider getting
help.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?33018>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/