Sometimes, you need some constraints for your DSL and you can use the grammar language for that. However, this is not a good idea. For example, in a previous post, I created a grammar rule to parse hexadecimal numbers with exactly two digits. To do this, we created the following rule:
Continue ReadingSometimes we have a value that has different representations. For example, an integer can be represented in base 10, base 2, base 16 or any other. Depending of the domain, one of these representations might mean more to the experts. Xtext allows to do this very easily. The full code for this example can be found here.
Continue ReadingIn a previous tip I showed how to add FQN support to your Xtext DSL. In this tip, we are going to customize our FQN to have a different separator. The full code for this example can be found here. The basic block language I am using the block language of the previous tip, but this time we are using the characters -> as separator
Continue ReadingXtext allows to easily add support for fully qualified names in your language. The full code for this example can be found here. The basic block language To illustrate this feature I will use a simple language to represent blocks. Each block has a name and can contain three members:
Continue ReadingXtend is a wonderful language. It is specially practical when traversing ASTs and it is the best option to generate code. However, it is “is no longer the Java 17 of today”, as Christian Dietrich (one of Xtext maintainers) put it in this thread. Hence, the recommended best practices for Xtend as of today are:
Continue Reading