[news.eclipse.technology.gmt] MOFScript: strange imports management in c

[Yannick <yannick@xxxxxxxxxxxxxxxx>]

Hi,

I noticed that MOFScript (1.1.5) has a strange behaviour for imports
management:

1)

At compilation, MOFScript doesn't detect bad rules' calls if that rule
exists in another transformation file (and transformation file isn't
imported)

For example, that is in main1.m2t :

texttransformation main1 (in uml:"http://www.eclipse.org/uml2/2.0.0/UML";) {

  uml.Model::main(){
	self.main1()

  }
  uml.Model::main1(){
	self.main2()
  }
}


And main2.m2t is in same folder or sub-folder of main1.m2t:

texttransformation main2 (in uml:"http://www.eclipse.org/uml2/2.0.0/UML";) {

  uml.Model::main(){
    stdout.println ("")
  }
  uml.Model::main2(){
  }
}

In file main1.m2t, I don't have a compilation error but I get a runtime
error during execution as expected.


2)

Cascading imports doesn't compile, I have to make all imports in the
main transformation file.

Example with 3 files:
main1.m2t -> imports main2.m2t (in a sub-folder)
main2.m2t -> imports main3.m2t (in sub-folder of main2.m2t)
main3.m2t -> no imports needed

In this case, I get compilation errors. But if I write all imports in
main1.m2t, it compiles.



Are those normal behaviour for MOFScript compiler?