On Sun, 5 Sep 2004, Clayton O'Neill wrote:
> This adds support for setting triggers on specific config variables.
> The basic idea is that you can register a named callback for any
> specific config variable. When that variable is set, all the
> callbacks registrered for that variable will be called to notify them
> that the new setting is available.
Neat. I haven't looked carefully at the implementation, but it sounds
like just the sort of call-back mechanism we'll need.
> I also fixed the solaris hints file to use the new trigger code. It
> sets a trigger on 'gcc_version' and when that gets set later on in the
> config, if it's defined, then the link command will be set to 'g++'.
I'd be inclined to call that particular routine solaris_gccversion_cb,
allowing for the likely need for other possibilities, such as
solaris_64_cb, solaris_sharedlibrary_cb, etc. I'm not sure offhand if
we'll need some sort of dependency information in case multiple triggers
get defined for a particular variable, but that could probably be added
later, if need be.
> I'm not sure this is the best solution either, but it shouldn't break
> as much stuff as my last patch, and adds some functionality that might
> be useful for other similar problems.
Actually it sounds like just the sort of thing I was looking for.
Thanks.
Andy Dougherty [EMAIL PROTECTED]
