This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Removing things from numbers.h


On 10 May 2000, Marius Vollmer wrote:

> Dirk Herrmann <dirk@ida.ing.tu-bs.de> writes:
> 
> > AC_ARG_ENABLE(debug-deprecated,
> >   [  --disable-debug-deprecated  Don't omit deprecated code for debugging],
> 
> I think it is technically sound to name the macro
> SCM_DEBUG_DEPRECATED, but I think it is confusing to name the option
> `--disable-debug-deprecated'.  What about `--enable-deprecated'?

You're right.  That's easier to understand.  Here's an improved, but still
not quite beautiful solution:



AC_ARG_ENABLE(deprecated,
  [  --enable-deprecated     Include deprecated code [not included by default]],
  if test "$enable_deprecated" = y || test "$enable_deprecated" = yes; then
    debug_deprecated=0
  else
    debug_deprecated=1
  fi,
  debug_deprecated=1)

AC_DEFINE_UNQUOTED(SCM_DEBUG_DEPRECATED, $debug_deprecated,
  [If 1: don't include deprecated code to help get rid of references to it.])



Still, does somebody know about a better autoconf way (for example a
special macro) to realize the following:

- if some feature is enabled, have the macro be defined as 1, otherwise as 0
- the same, but vice versa, like in the above example.

If we go ahead with SCM_DEBUG_ options in that way, this will become a
common pattern.

Best regards
Dirk Herrmann


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]