Re: --enable-api-default-signal-handlers in glibmm 2.10.6

["Jonathon Jongsma" <jonathon jongsma gmail com>]

On 9/26/06, Matt Hoosier <mwhoosier gmail com> wrote:
> Hi,
>
> The M4 macro (from scripts/reduced.m4) which controls whether default
> signal handlers will be exposed as virtual functions seems to have a
> typo:
>
> AC_DEFUN([GLIBMM_ARG_ENABLE_API_DEFAULT_SIGNAL_HANDLERS],
> [
>   AC_ARG_ENABLE([api-exceptions],
>       [  --enable-api-default-signal-handlers  Build default signal
> handlers API.
>                               [[default=yes]]],
>       [glibmm_enable_api_default_signal_handlers="$enableval"],
>       [glibmm_enable_api_default_signal_handlers='yes'])
>
>   if test "x$glibmm_enable_api_default_signal_handlers" = "xyes"; then
>   {
>     AC_DEFINE([GLIBMM_DEFAULT_SIGNAL_HANDLERS_ENABLED],[1], [Defined
> when the --enable-api-default-signal-handlers configure argument was
> given])
>   }
>   fi
> ])
>
> Note that the AC_ARG_ENABLE clause uses "api-exceptions" as the
> salient bit, when I guess it should probably be
> "api-default-signal-handlers". This has the effect that
> $glibmm_enable_api_default_signal_handlers never takes on the "yes"
> value, and the virtual functions are never enabled.

Thanks.  I've opened a bug about this so that it doesn't get lost (i'm
not at home now so I can't investigate at this moment)
http://bugzilla.gnome.org/show_bug.cgi?id=357830

--
jonner