This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Sep 27 2012, Jeff Squyres (jsquyres) wrote:
> Fwiw, we have put in many hours of engineering to "that obscene hack"
> *because* compilers all have differing degrees of compatibility suck.
> It's going to be years before compilers fully support f08, for example,
> so we have no choice but to test for various compiler characteristics at
> configure time.
Yes and no, but that wasn't my point anyway. My remarks about the
obscene hack were to the configure mechanism more than its use - I
could describe why I said what I said, but it's not relevant.
> So I'm ok propagating "that obscene hack" when it protects users and
> prevents wasting time on mailing list questions.
That wasn't my point. It may well be the lesser of two evils, given
the world that we are in. It was that there really isn't worth having
a kludge around every little compiler lunacy. Realistically, in the
year 2012, if any Fortran compiler doesn't support Fortran 95 properly,
it should be categorised as defective/obsolescent and only the old
In this case, I doubt very much that Oracle's compiler doesn't support
PRIVATE, and I would definitely bet on the problem being caused by
some defect in the configure mechanism. If it isn't, it's almost
certainly some OTHER issue that shows up as a failure with PRIVATE.
Fixing it by putting yet another hack into configure is definitely
not the right solution.