Clayton O'Neill <[EMAIL PROTECTED]> wrote:
> This adds support for setting triggers on specific config variables.
Thanks, applied finally, except the order of calling gcc.pl, which
already changed in the meantime and is (hopefully) correct already.
leo
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> "imcc/imcc.l", line 852:
> warning: improper pointer/integer combination: arg #2
Is already fixed.
> Still, it's probably a good step forward.
Ok.
leo
On Tue, 7 Sep 2004 10:50:49 -0400 (EDT), Andy Dougherty
<[EMAIL PROTECTED]> wrote:
> Still, it's probably a good step forward. We might eventually decide we
> need pre- and post- triggers or other enhancements, but this is probably a
> good basis to start with.
Pre and post triggers would be pret
On Tue, 7 Sep 2004, Leopold Toetsch wrote:
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Sun, 5 Sep 2004, Clayton O'Neill wrote:
>
> >> This adds support for setting triggers on specific config variables.
>
> > I'd be inclined to call that particular routine solaris_gccversion_cb,
>
> Should
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Sep 2004, Clayton O'Neill wrote:
>> This adds support for setting triggers on specific config variables.
> I'd be inclined to call that particular routine solaris_gccversion_cb,
Should the patch go in?
> Thanks.
> Andy Dougherty
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 cal
Attached is a patch that should fix the solaris link issues without
breaking every other platform, hopefully. ;)
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 s
