[Omake] Should we provide AC_MSG_* and other
autoconf-style functions?
Nathaniel Gray
n8gray at caltech.edu
Thu Feb 15 21:24:31 PST 2007
On Feb 15, 2007, at 8:37 PM, Aleksey Nogin wrote:
> On 15.02.2007 17:27, Nathaniel Gray wrote:
>
>> I like the idea of more configuration functions, but I'm not so
>> hot on
>> the autoconf-style names.
>
> What naming scheme would you propose?
>
> So far I have added the following - AC_MSG_CHECKING AC_MSG_ERROR
> AC_MSG_FOUND AC_MSG_RESULT AC_MSG_WARN AC_MSG_YES_NO AC_RUN_PROG
> AC_TRY_COMPILE AC_TRY_LINK AC_TRY_RUN
I would propose the usual omake convention of camelcase, possibly
replacing AC with something like Conf:
ConfChecking, ConfMsgError, ConfMsgFound, etc.
>>
>> Perhaps you could put them in an autoconf.om
>> compatibility module?
>
> Well, they are not that compatible - it's really more
> autoconf-style/autoconf-inspired.
If they're not compatible then it's probably a bad idea to keep the
autoconf names. It would just lull autoconf-familiar people into a
false sense of security.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
More information about the Omake
mailing list