autoconf
[Top][All Lists]
Advanced

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

Re: Interface of AC_F77_DUMMY_MAIN


From: Akim Demaille
Subject: Re: Interface of AC_F77_DUMMY_MAIN
Date: 17 Jul 2001 10:09:30 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Academic Rigor)

>>>>> "Steven" == Steven G Johnson <address@hidden> writes:

Steven> On 12 Jul 2001, Akim Demaille wrote:
>> AC_F77_DUMMY_MAIN (action-if-fail, action-if-none, action-if-found)
>> 
>> I have a problem at least with the order here.  I'd prefer
>> 
>> action-if-found, action-if-none, action-if-fail
>> 
>> and I would even prefer to have
>> 
>> action-if-found, action-if-not-found (= if-fail)
>> 
>> and have an official var left to the user to perform her tasks, say
>> $F77_DUMMY_MAIN.  This is more conventional in Autoconf.

Steven> The reason I put action-if-fail first was because I figured
Steven> that it would be the one the user is most likely to override.

I understood that, but the unity of the whole interface is more
important.


Steven> On the other hand, the default action-if-found is to AC_DEFINE
Steven> F77_DUMMY_MAIN, and the user almost certainly does *not* want
Steven> to override this, since F77_DUMMY_MAIN is required for future
Steven> link tests (e.g. AC_F77_WRAPPERS) to function.  It would be
Steven> annoying to have to duplicate this if you only want to
Steven> override action-if-fail.

I struggled to have Autoconf depend as little as possible on $#, so
being defaulted is unrelated to being last or not.

Steven> Suggestions?

I still propose what I suggested above: two actions, and a means for
the user to read the name of the dummy main, empty standing for not needed.



reply via email to

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