From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,4c17e6ae73bd8c51 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!feedme.ziplink.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Ada and UML Date: Fri, 03 Sep 2010 20:39:51 +0100 Organization: A noiseless patient Spider Message-ID: References: <4c7f5735$0$6766$9b4e6d93@newsspool3.arcor-online.net> <156c1bf7-8744-43a0-b620-017244d4763d@k17g2000prf.googlegroups.com> <2b5347b3-219b-4049-a1e5-bc5f5937c4cc@m17g2000prl.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Date: Fri, 3 Sep 2010 19:39:53 +0000 (UTC) Injection-Info: mx03.eternal-september.org; posting-host="KCXegvZb5vh43D+f3BR6Ew"; logging-data="874"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18M6LUxnWt/f6wsY893zCPSkk3BBb3eix4=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin) Cancel-Lock: sha1:mopWCLYTONO5GubfoHvFq8wtDQw= sha1:Uv6BdImYhqsmBYjPoTSDFLJBzqE= Xref: g2news1.google.com comp.lang.ada:13935 X-Original-Bytes: 2530 Date: 2010-09-03T20:39:51+01:00 List-Id: Matteo Bordin writes: > I personally think that scripting languages such as Acceleo (or xPand > or similar) are ok just for very simple code generators because they > cannot easily handle persistent datastructures. I cannot imagine > writing a code generator for xUML or for synchronous languages in > Acceleo... I don't know Acceleo (clearly something to look at!), but from experience with XSLT I'd say that it's much easier with model-to-model transformations. By that I mean, XSLT will easily translate XML to code if the structure of the XML is a close match to that of the code. But if you omit (as I did) the transformation from the structure that matches the UML tool's needs to this more convenient structure, you end up doing a lot of work in a language that's not well suited to it. For example, you wouldn't want a state machine where the same event triggered more than one transition from a given state. This and related checks took ~100 lines of hairy XSLT in ColdFrame (http://coldframe.sourceforge.net/).