Re: [patch] Automake backend parser script and others
- From: Gustavo Giráldez <gustavo giraldez gmx net>
- To: JP Rosevear <jpr ximian com>
- Cc: Gnome Devtools list <gnome-devtools gnome org>
- Subject: Re: [patch] Automake backend parser script and others
- Date: 10 Jul 2002 18:24:28 -0300
Hi JP,
On Wed, 2002-07-10 at 14:03, JP Rosevear wrote:
> On Fri, 2002-06-28 at 01:14, Gustavo Giráldez wrote:
> > The most important thing I think it's missing (and what I'll work on
> > next) is, after project modifications, to reparse changed groups and
> > make the backend read them again. This is because you can't really know
> > how will a modification affect other targets, and because I think it's
> > safer to do it this way (no sync problems between the project model and
> > the actual files). Any ideas on how to do this are very welcome,
> > specially how to inform the controls a group has changed. I was
> > thinking on using the event source, but I'm not sure at all.
>
> Yes, use the event source, this was the intended plan.
Ok, great.
> > May I commit?
>
> Yes, patch approved with one caveat - what flexibility are you gaining
> using the C structs and then converting to corba structs in order to
> respond to calls?
Most importantly I needed to keep configuration for each group and
target (the GbfAmConfigMapping type) which is not visible to the idl.
Also for target sources I have some more information which the script
provides, such as the dependency target in case the file is generated
from other target (again not in the idl for simplicity).
I don't like it to generate the corba struct on request myself, since
it's far from optimal, but I thought mixing them with the other
information in some struct wouldn't be nice/clean either. If you have
some other idea on how to do this I'll rework the patch. Otherwise,
I'll commit as it is now.
Regards,
Gustavo
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]