Changes for page Kieler Compiler
Last modified by Richard Kreissig on 2023/09/14 10:52
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Kieler Compiler (KiCo)1 +Kieler Compiler - Content
-
... ... @@ -1,5 +1,15 @@ 1 1 = Kieler Compiler (KiCo) = 2 2 3 +{{panel title="Project Overview" borderStyle="dashed"}} 4 +Responsible: 5 + 6 +* [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]], Steven Smyth 7 + 8 +Related Theses: 9 + 10 +* none yet 11 +{{/panel}} 12 + 3 3 In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent. 4 4 5 5 ... ... @@ -26,11 +26,14 @@ 26 26 1. Add the extension 27 27 28 28 29 -{{{de.cau.cs.kieler.kico.transformation}}} 39 +{{{de.cau.cs.kieler.kico.transformation}}}((( 40 + 41 +))) 42 +1. ((( 43 +Add one of the following extension element 30 30 31 -Add one of the following 32 - 33 33 [[image:attach:KiCo2.jpg]] 46 +))) 34 34 35 35 |=((( 36 36 Extension Element ... ... @@ -68,8 +68,106 @@ 68 68 * name: An optional String name for this transformation. If nothing is entered here the ID will be used as a name. 69 69 ))) 70 70 84 +=== Example === 85 + 86 +{{code title="plugin.xml"}} 87 + <extension 88 + point="de.cau.cs.kieler.kico.transformation"> 89 + <transformationGroup 90 + id="NORMALIZE" 91 + dependencies="TRIGGEREFFECT, SURFACEDEPTH" 92 + name="Transform All Normalize"> 93 + </transformationGroup> 94 + </extension> 95 + <extension 96 + point="de.cau.cs.kieler.kico.transformation"> 97 + <transformationMethod 98 + class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation" 99 + id="TRIGGEREFFECT" 100 + method="transformTriggerEffect" 101 + name="Transform Trigger and Effect"> 102 + </transformationMethod> 103 + </extension> 104 + 105 + <extension 106 + point="de.cau.cs.kieler.kico.transformation"> 107 + <transformationMethod 108 + class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation" 109 + id="SURFACEDEPTH" 110 + method="transformSurfaceDepth" 111 + name="Transform Surface Depth"> 112 + </transformationMethod> 113 + </extension> 114 + 115 + <extension 116 + point="de.cau.cs.kieler.kico.transformation"> 117 + <transformationGroup 118 + id="ALL" 119 + dependencies="CORE NORMALIZE" 120 + name="Transform All"> 121 + </transformationGroup> 122 + </extension> 123 +{{/code}} 124 + 71 71 72 72 73 73 == Compilation == 74 74 75 -text 129 +Once a bunch of model transformations are registered, these can simply be called using the KiCo central "KielerCompiler" class with its method compile(). This will be given a List<String> of transformation IDs or a comma separated String of transformation IDs as the first parameter. The second parameter is the EObject that is being transformed. It should meet the signature of the first model transformation called. Note that the actual model transformations that are done may vary because KiCo will automatically inspect the dependencies of each transformation requested (deep-recursively). If you do not like this to happen as an advanced user you can use a third parameter that will skip this autocompletion. Note that if you switch this off also NO transformation groups can be processed. Here is an overview and examples how to use the compile() method: 130 + 131 +|=((( 132 +Method 133 +)))|=((( 134 +Description 135 +))) 136 +|((( 137 +\\ 138 + 139 +{{{EObject KielerCompiler.compile(List<String> transformationIDs, EObject eObject)}}} 140 +)))|((( 141 +* transformationIDs: List of Strings representing the transformation IDs and a pre-ordering. Note that KiCo may automatically modify the order to meet the dependencies of the referenced transformation IDs or transformation group IDs. 142 +* eObject: The EObject that is the input to the compilation process. 143 +* Returns: The EObject returned from the last model transformation called by KiCo. 144 +))) 145 +|((( 146 +\\ 147 + 148 +{{{EObject KielerCompiler.compile(String transformationIDs, EObject eObject)}}} 149 +)))|((( 150 +This is a convenient method only which can be used to give transformation IDs or transformation group IDs as a comma separated String. For eObject and the return value see above. 151 +))) 152 +|((( 153 + 154 +\\ 155 + 156 +{{{EObject KielerCompiler.compile(List<String> transformationIDs, EObject eObject, boolean autoexpand)}}} 157 +)))|((( 158 +This is an advanced compile method which can turn of auto-expansion with the last parameter. Use this with care! Note that if switching autoexpand off you cannot use transformation group IDs any more. Also no dependencies will be considered. The transformations will be applied straight forward in the order defined by the transformationIDs list. 159 +))) 160 + 161 +=== Examples === 162 + 163 +{{code title="Java Code"}} 164 +import de.cau.cs.kieler.kico.KielerCompiler; 165 +... 166 +private MyEObjectClass myMethod(EObject eObject) { 167 + ... 168 + transformed = (MyEObjectClass) KielerCompiler.compile("ABORT, SIGNAL", eObject); 169 + ... 170 + return transformed 171 +} 172 +{{/code}} 173 + 174 +{{code title="Xtend Code"}} 175 +import de.cau.cs.kieler.kico.KielerCompiler 176 +... 177 +def dispatch MyEObjectClass myMethod(EObject eObject) { 178 + transformed = KielerCompiler.compile("ABORT, SIGNAL", eObject) as MyEObjectClass 179 + ... 180 + transformed 181 +} 182 + 183 + 184 + 185 + 186 +{{/code}}
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -94700 611 +9470073 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/94700 61/Kieler Compiler(KiCo)1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470073/Kieler Compiler