autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation for new FC Fortran macros


From: Steven G. Johnson
Subject: Re: Documentation for new FC Fortran macros
Date: Wed, 8 Oct 2003 16:09:18 -0400 (EDT)

On Wed, 8 Oct 2003, Akim Demaille wrote:
>  > Attached is a revised patch for autoconf.texi without the @node mangling.
> 
> Great, please install when you want.

Thanks, will do.

>  > +The autoconf Fortran support is divided into two categories: legacy
> 
> autoconf is an executable.  You mean the package, hence _A_utoconf.

Okay.

>  > address@hidden AC_PROG_F77_C_O/AC_PROG_FC_C_O
> 
> Please, use @defmacx instead.

Okay; I've used @defmacx everywhere.  (This is a new tag for me.)

> But anyway, this macro is an error, it has no application AFAIK.
> Historically even AC_PROG_CC_C_O was very dubious, and was tailored
> for GNU Make (that's why not only does it check $CC, but cc too).  I
> fail to see the need to propagate it.  Who uses it anyway?

I'm not sure who uses it (although I remember that at one point the Cray
Fortran compiler didn't support -c -o).  I made AC_PROG_FC_C_O because it
wasn't really any effort, and I didn't know whom it would harm to omit.

Maybe we should add a sentence to all of the _C_O macros (CC
included) saying that the macro is deprecated and that people who need it
should speak up.

>  > +By default, the FC macros perform their tests using a @file{.f}
> 
> If you mean to use FC like this in the text body, it ought to be
> @code{FC} then.  Several occurrences.

Ok.

>  > +To check for a syntax feature of the (C, C++, Fortran, or Fortran 77) 
> compiler,
> 
> Do we really need to keep F77?  Or actually, do we need to keep this
> language list at all?  I would remove it.

We do need to keep F77.  The point is that F77 is basically a completely
different language from Fortran 9x, and people sometimes need to compile
both simultaneously (this issue came up every time Fortran 9x support was
discussed on the autoconf mailing list).  Hence the need for both the F77
legacy macros and the newer FC macros, and thus both Fortran and Fortran
77 languages.

But, as for this particular line, I've changed it to:

+ To check for a syntax feature of the current language's (@pxref{Language
+ Choice}) compiler, such as whether it recognizes a certain keyword, or

> Likewise, I would go to a more robust
> 
>       This macro uses the appropriate compilation flags for the
>       current language (@pxref{The place where these guys are
>       defined}).

I've put the flags under the "Language Choice" section, and changed the
places you complained about to point to this section instead.

Steven





reply via email to

[Prev in Thread] Current Thread [Next in Thread]