{"issue":{"state":"closed","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/50701825ddf1417b97e8a63e1322d1af?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"50701825ddf1417b97e8a63e1322d1af","url":"https://api.github.com/users/brice-morin","login":"brice-morin","id":576169},"assignee":null,"updated_at":"2011-10-31T20:14:46Z","labels":[{"name":"Compilers","color":"e10c02","url":"https://api.github.com/repos/ffleurey/ThingML/labels/Compilers"},{"name":"ThingML Language","color":"02e10c","url":"https://api.github.com/repos/ffleurey/ThingML/labels/ThingML+Language"}],"closed_at":"2011-10-31T20:14:46Z","comments":0,"url":"https://api.github.com/repos/ffleurey/ThingML/issues/8","body":"What is the advised strategy to deal with multiple target languages? Currenly ThingML compiles to C, Scala, etc. ThingML allows to define extern expressions (eg, by directly writing some C, when needed eg, for system calls). It's however quite a pain to duplicate all the models where extern statements are involved (eg, to change \"millis()\" by \"System.currentTimeMillis()\"). This goes against the MDE practices ThingML advocates... ;-)","html_url":"https://github.com/ffleurey/ThingML/issues/8","title":"Strategy to deal with multiple target languages?","number":8,"id":1403238,"created_at":"2011-08-14T14:46:21Z"},"action":"closed"}