<br><font size=2 face="sans-serif">Dear Gabriele,</font>
<br>
<br><font size=2 face="sans-serif">You are correct, every time you invoke
the GReAT Master interpreter the Meta files are regenerated. However, the
problem is not easy to solve.</font>
<br>
<br><font size=2 face="sans-serif">When the interpreter is invoked there
is no way for the interpreter to know which part of the model was edited
and thus unable to decide which sub interpreter to invoke or leave out.
Thus GReAT takes the conservative approach and generates everything again.
</font>
<br>
<br><font size=2 face="sans-serif">If you want a more fine grain control
you can choose not to call the "master interpreter" but instead
call the sub interpreters as the situation warrants. For example, if you
have only changed the transformation and not touched either the metamodels
or the configuration you should call Generate GR (from the file -->
run interpreter menu) . Similarly, if you only change the metamodel and
not the transformations you should invoke the UML2XML interpreter and for
the configuration file the Generate config interpreter should be invoked.</font>
<br>
<br><font size=2 face="sans-serif">Another option we had discussed but
hasn't been implemented yet is to provide check boxes in the GReAT master
interpreter that allows the user to choose which interpreters he/she wants
to invoke. </font>
<br>
<br><font size=2 face="sans-serif">Someone in the GReAT team please confirm
these suggestions or reply with the reason for this not working.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br>
<br><font size=2 face="sans-serif">Adi</font>
<br><font size=2 face="sans-serif">-----------------------------------<br>
Aditya Agrawal<br>
Researcher<br>
IBM T. J. Watson<br>
mailto:aagrawa@us.ibm.com<br>
+1 (914) 784-6068 (TL 863)<br>
</font>
<br>
<br><font size=2><tt>great-users-bounces@list.isis.vanderbilt.edu wrote
on 11/14/2004 09:21:54 PM:<br>
<br>
> Whatever minimal change the user performs on a transformation, when
s/he <br>
> invokes the GReAT Master Interpreter ALL the UDM files are rewritten
and <br>
> then they are recompiled at the first invocation of the transformation.<br>
> <br>
> With the default /O2 compiler settings my transformation takes something
<br>
> like 15 minutes to compile (a big PICML.cpp). This is not reasonable
<br>
> when the user is developing and debugging a transformation and would
<br>
> like to recompile and retry the transformation quickly. When I hack
by <br>
> hand the compiler flags putting /Od it takes 2 minutes to compile,
but <br>
> with the previous version of GReAT it was taking just 10 sec or the
<br>
> like. This seems a significant degrade of usability for GReAT to me.<br>
> <br>
> At least the GReAT Master Interpreter should check for each file if
the <br>
> new version of the file it's replacing is identical byte by byte to
the <br>
> previous one and in that case do something to avoid recompiling that
<br>
> file at the next invocation of the transformation<br>
> <br>
> Thanks,<br>
> Gabriele<br>
> _______________________________________________<br>
> great-users mailing list<br>
> great-users@list.isis.vanderbilt.edu<br>
> http://list.isis.vanderbilt.edu/mailman/listinfo/great-users<br>
</tt></font>