Jakob Høgenes
Jakob Høgenes
As discussed, we should introduce _assertions_ in the metamodel, that is, checks that are evaluated at run-time. The first concrete example of this is to assert that messages are handled...
IMO, the ThingMLCompiler and Context classes have turned into a bit of a mess, with references to directories or other things being set all over the place. I think it...
There are some things that would be nice to have included in the ThingML toolchain when it comes to standard functionality, that does not quite fit into the action language,...
This is mostly sugar, but is one of the parts I like a lot about languages like Go and Python, and it would not take a lot of work to...
While writing ThingML models in Eclipse, the process of finding the right file with the `configuration` -> right-click -> ThingML -> Select compiler, is tedious and slightly annoying (if you...
The Eclipse UI should automatically show the ThingML-console when code is generated, like other plugins show their own console when you run configurations. Small fix, but would save a few...
Since the UML compiler is both very useful and used quite a lot, it might make sense to run tests on that compiler as well. It would probably be too...
Properties declared within states, should be re-initialized to their initial value (_init expression_) on every entry of the state, __unless__ the current or parent (just the immediate) keeps history. This...
As far as I can remember from our discussion last week regarding state properties, the proper behaviour was that their value was initialized when the containing state is *entered* (I...
Quite a lot of places throughout the code, we print stuff using `System.out` and `System.err`. This doesn't work very well in places where we either don't care about that output,...