Hi there,

thank for the new versions of the files.

Now we are facing another problem regarding the order of definitions
and uses of variables. The reference manual of DAVE-ML states that
"variableDefs should appear in calculation order" (page 9 of v. 1.9b2).

That "should" is a requirement or just a good practice suggestion?

In the F16 dml there are two cases of variables used before they are
defined (details by G. Mirri are in the following).

I suppose that, at this point in the development of DAVE-ML, the true
requirement is that definitions and uses may appear not in order, but an
ordering must be possible:
- writing them in order is just a good practice for the readability of
  the XML;
- if an ordering is not possible (there is a cycle) the DAVE-ML is not
  valid.

Is this right?

Thanks in advance,
Giovanni A. Cignoni.


-------------------------------------------------------------------------------

F16_aero.dml Revision: 108

 - line 372: definition of variable "cl1" refers to variable "clt" in
the calculation block (at line 379), but variable "clt" is not yet defined
   (it will be defined later at line 488);

 - line 395: definition of variable "cn1" refers to variable "cnt" in
the calculation block (at line 402), but variable "cnt" is not yet defined
   (it will be defined later at line 519).

Reply via email to