using %opAlias% macro in transformations

[Martin Darilek]

In our projects (in analytic models) we are using class/attribute/operation names for analytic name and alias for future design names. Now I'm writing some custom transformations (PIM -> PSM C#) where class/attribute/operation aliases and names are swapped. Transformation process is OK but after this I recieve message "There was an error parsing <temp_filename_is_here> on line XXX. Unexpected symbol: alias". I found that operation alias is meant there. Is it bug? Here is transformation code:

Code: [Select]


Operation
{
 %TRANSFORM_REFERENCE()%
 %TRANSFORM_CURRENT("name","alias","type")%
 name=%qt%%opAlias%%qt%
 alias=%qt%%opName%%qt%
 type=%qt%%CONVERT_TYPE("C#",opReturnType)%%qt%
%list="Parameter" @separator="\n" @indent="  "%
}

and here is result (problematic part only):

Code: [Select]


Operation {
 XRef{namespace="C#" name="Operation" source="{FD5EA275-3E1A-4f3c-87AE-F6CE55A36A06}"}

           stereotype=""

           notes=""

           code=""

           scope="Public"

           name="designName"

           alias="analyticName"

           type="void"

}


[Eve]

Yes, it's a bug.  The parser for the intermediary language isn't expecing an operation alias.  We'll get that fixed for the next build.