Changes for page Kieler Compiler

Last modified by Richard Kreissig on 2023/09/14 10:52

From version 4.1
edited by cmot
on 2014/03/16 21:53
Change comment: There is no comment for this version
To version 13.1
edited by cmot
on 2014/03/17 11:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Kieler Compiler (KiCo)
1 +Kieler Compiler
Content
... ... @@ -1,3 +1,13 @@
1 +{{panel title="Project Overview" borderStyle="dashed"}}
2 +Responsible:
3 +
4 +* [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]], [[Steven Smyth>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/ssm/||shape="rect"]]
5 +
6 +Related Theses:
7 +
8 +* none yet
9 +{{/panel}}
10 +
1 1  = Kieler Compiler (KiCo) =
2 2  
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.
... ... @@ -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
... ... @@ -113,4 +113,123 @@
113 113  
114 114  == Compilation ==
115 115  
116 -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&#x3c;String&#x3e; 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&#x3c;String&#x3e; 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}}
187 +
188 +== Help / Problems / FAQs ==
189 +
190 +Maybe you get into problems when using KiCo. The following list should give you hints to solve these. If you have a problem not considered here please write us an e-mail (see above for contact information of the persons in charge of KiCo).
191 +
192 +|=(((
193 +Symptom
194 +)))|=(((
195 +Reason
196 +)))|=(((
197 +Solution
198 +)))
199 +|(((
200 +You get the following run time error:
201 +
202 +
203 +\\\\\\\\\\\\\\\\[[java:102>>url:http://java:102||shape="rect"]]
204 +[[java:136>>url:http://java:136||shape="rect"]]
205 +[[java:164>>url:http://java:164||shape="rect"]]\\
206 +
207 +{{{ENTRY de.cau.cs.kieler.klighd 4 0 2014-03-17 11:08:46.009!MESSAGE !STACK 0java.lang.RuntimeException: Cannot find a transformation with the ID 'ABORT2'. Make sure that the transformation with this ID is registered and its declaring plugin is loaded. Make sure that the ID does exactly match (case sensitive). Maybe you forgot to separate multiple ID's by a comma.    at de.cau.cs.kieler.kico.KielerCompiler.getTransformation(KielerCompiler.java:61)    at de.cau.cs.kieler.kico.KielerCompiler.getDependencies(KielerCompiler.java:82)    at de.cau.cs.kieler.kico.KielerCompiler.isDependingOn(KielerCompiler.)    at de.cau.cs.kieler.kico.KielerCompiler.insertTransformationID(KielerCompiler.)    at de.cau.cs.kieler.kico.KielerCompiler.expandDependencies(KielerCompiler.)...}}}
208 +)))|(((
209 +There is a transformation with ID "ABORT2" referenced
210 +either by the initial call to KielerCompiler.compile() or
211 +by some of the dependent transformations /
212 +transformation group.
213 +
214 +But KiCo could not find any registered transformation
215 +with ID "ABORT2".
216 +
217 +Maybe the plugin declaring "ABORT2" was not loaded
218 +or the ID is misspelled.
219 +
220 +
221 +)))|(((
222 +Check why "ABORT2" may not be found
223 +by KiCo, more specifically, check if the
224 +declaring can be loaded (sometimes
225 +compiler error prevent it from being loaded
226 +or it has unsatisfied dependencies).
227 +Also check the spelling of the ID, maybe
228 +the declaring plugin defines the transformation
229 +with the ID "abort2".
230 +)))
231 +|(((
232 +You get the following error:
233 +
234 +{{{!ENTRY de.cau.cs.kieler.kico 2 2 2014-03-17 11:26:13.818}}}
235 +
236 +\\
237 +
238 +{{{!MESSAGE Extension 'TERMINATION' from component: de.cau.cs.kieler.sccharts cannot beloaded becaus this ID is already taken. (de.cau.cs.kieler.kico)}}}
239 +)))|(((
240 +The trasformation with ID "TERMINATION" is already
241 + registered and this ID cannot be used a second time.
242 +The component "de.cau...sccharts" tries to register
243 +a transformation with this ID while this ID is already
244 +taken.
245 +)))|(((
246 +Rename one of the IDs or form a group of
247 + transformations.
248 +)))
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9470063
1 +9470083
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470063/Kieler Compiler (KiCo)
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470083/Kieler Compiler