The naming of modeling concepts was taken directly from XML to make
generators easy to make: a generator uses domain concept names while accessing the
model and producing the required output. As XML required a special naming policy,
domain concept names using a capital letter were changed to lower case. Generating
XML is problematic for reserved words and white spaces in entries. For the former,
regular expressions were used to describe legal text strings and for the latter a
generator was de?¬?ned to make entry values legal in XML (e.g., remove spaces from
domain concept names).
To produce the conditions in the same order, the generator ?¬?rst produces the default
path information followed by the ???otherwise??? path. The generator implements this by
using the metamodel data??”access ?¬?rst the default path and then the otherwise path.
For CPL this was an adequate and simple solution. If different path execution orders
had needed to be speci?¬?ed, then the path choice could have been given to the
relationship as a property describing the path. Giving a number to the relationship path
is one approach. If there are only two paths from the switch, or if it is relevant to
describe the execution order only for one of the many paths, such as default, ?¬?rst, and
so on, marking just one path is enough.
Pages:
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235