Hi,
Am 14.10.2015 um 11:50 schrieb Mario Gazzo:
> Thank you Peter,
>
> I appreciate the extensive explanation and the suggestions for a workaround
> in the other mail you posted. It clarifies things quite a bit for me. I look
> forward to the new language features though, any timeline for this y
Thank you Peter,
I appreciate the extensive explanation and the suggestions for a workaround in
the other mail you posted. It clarifies things quite a bit for me. I look
forward to the new language features though, any timeline for this yet?
I can share some insights on how we use Ruta in our s
Hi Mario,
Am 13.10.2015 um 12:17 schrieb Mario Gazzo:
> Hi Peter,
>
> Thank you for answering. I fully understand that you may both be busy and
> that systems can come in between sometimes. I am subscribing to the user list
> though.
>
> Regarding your question. There is only a single MatchedReg
Hi,
I think this is the same problem. The CREATE action just searches in its
match context. I will answer the context question is the other mail.
Best,
Peter
Am 11.10.2015 um 16:21 schrieb Mario Juric:
> I am still struggling with the use of variables in some CREATE statements.
> The features
Hi Peter,
Thank you for answering. I fully understand that you may both be busy and that
systems can come in between sometimes. I am subscribing to the user list though.
Regarding your question. There is only a single MatchedRegexAnnotation in that
example, which is the one that gets assigned t
Hi,
sorry for the delayed response. I received your mail just yesterday.
Maybe your mail needed to be moderated. Did you subscribe to the user list?
Here's a first short answer. I will try to look into it in more details
if this does not help:
The CREATE action searches for annotations (that sho
I am still struggling with the use of variables in some CREATE statements. The
features do not always have the expected values after CREATE. Let me give
another more concrete example:
TYPE pmcIdentifier;
BLOCK(ForEach) IdentifierAnnotation.propertyName=="PMC"{} { // Just capturing
scope
Ide
Hi,
I have a annotation type variable that I am assigning a value in a statement
block and then use that value in match rule to set the attribute in a new
annotation like this:
Type myvar;
BLOCK(ForEach) UniqueMatch{} { // Capturing unique scope with this
“Some (\\w+) Regex" -> 1 = Matched
