| EVL: Defining more than one context with the same name in a module [message #1732394] |
Mon, 16 May 2016 15:32  |
Eclipse User |
|
|
|
Hi all,
I have an EVL module which has defined contexts like "A" more than one. Of course, all of the constraints of the defined "A" contexts are different, i.e., there is no common constraints between contexts with the same names:
context A {
...
}
context A {
constraint X {
...
}
}
context B {
constraint Y {
check: self.satisfies('X', ...) // Erroneous: constraint X not found
...
}
}
1) Does the above scenario is valid for a module definition in the EVL language?
2) An strange error, here in the constraint 'Y' in the context B, Constraint 'X' not found! , is displayed during the launch of the above module while the 'X' constraint is defined in one of those contexts which have the same names. Of course, this is a problem for constraints which are defined in other contexts (here context A) than the satisfaction statement used context (here context B)!
Is there any trick to resolve this issue and yet keep the above situation? In other words, is there a statement similar to Context.allInstances().exists(c | c.satisfies('X', ...)) for replacing the statement self.satisfies('X', ...) in the constraint 'Y'.
Best regards,
Alireza
[Updated on: Tue, 17 May 2016 08:13] by Moderator |
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.25886 seconds
Home