MPS build #798 is out

We released a new build. The most important changes:

• Behavior and constraints aspects are separated
• Editor language was refactored. We have a system which is similar to CSS
• Base language editor improvements. Now it behaves more similar to its IntelliJ IDEA’s counterpart
• Plugin language is better integrated with IDEA platform

You can download it from here

MPS build #718

We’ve released a new MPS build. The main change is transition to IntelliJ IDEA platform: framework for creating IDEs

You can download it from here

There is no MPS plugin for IDEA which enables to work with Java and MPS from the same IDE but we have plans to create one.

MPS Build #607

MPS build #607 is out. As usual you can download it from here here

MPS build #579 is out

We released a new build. New features:

• improved model properties dialog (automatic import of models/languages on module level)
• devkits refactored
• simplification of classpaths in modules
• auto resolver
• unit test runner
• todo view and todo highlighting in mps
• icons in plugin actions

As usual you can download it from here

Simple Base Language Extension Screencast

We have created a new screencast about MPS. This time it’s about a simple BaseLanguage extension. In it we not only show language extension but the features which are inaccessible in programming languages with metaprogramming support: custom type system and data flow analysis. You can watch it here

“The Simplest Language” screencast

We’ve create a screencast on which you can see how to create a simple language in JetBrains MPS. You can find it here

MPS build #531 is out

MPS build #531 is out.
Among new features and improvements:

• Improved entering of code. Intelligent input mechanism is more intelligent. For example, it’s possible to enter System.out. without pressing control+space. When you press ” you will have a string where you can start typing just like in IntelliJ IDEA
• Improved data flow language. All the baseLanguage constructs are checked with it.
• Extract method refactoring (you can activate it in baseLanguage extensions from popup menu or with control+alt+M) shorctut.

As usual, you can download it from: http://www.jetbrains.net/confluence/display/MPS/JetBrains+MPS+Download+Page

Updated “Getting started” how to for MPS

One of our EAP users, Tracy Snell have update “Getting started” how to to the current state of MPS. You can find it here. We weren’t updating it because now we have better examples and screencasts which cover MPS’s features more thoroughly but anyway this example can be useful if you want to create simple working language in a short period of time.

Data Flow Analysis In JetBrains MPS

Data Flow analysis allows us to perform a lot of handy checks: we can find unused assignments, access to uninitialized variables, and it’s hardly possible to implement extract method refactoring without it. All in all, it dramatically improves experience of working with IDE. Of course we at JetBrains have implemented it in our meta-programming system and of course we created a language which can be used to describe data flow aspect of a language

In order to support data flow analysis in your language, you have to represent constructs of a language in terms of elementary instructions. Among them are:

• read x - accesses variable x
• write x - writes to variable x
• jump p - unconditionally jumps to position p
• ifjump p - conditionally jumps to position p
• ret - return from current program

As you can see, these instructions are quite simple. It’s impossible to write a working program with them but for the kinds of data flow analysis we are interested in they are more than enough.

Let’s consider a simple example. Here is a code for do..while loop:

First we insert code for a loop’s body with “code for” statement. Then we insert code for condition. After evaluating condition, we perform conditional jump to the start of code for a while statement. Gray braces represent code which can be unreachable (we perform reachability analysis using these instructions graph). As you can see, this code is very simple and domain specific.

Let’s consider a more complex example: switch statement

First, we evaluate expression which value we switch on. Then we add conditional jumps to starts of case blocks. Finally, we add code for default case:

P.S. Almost all of this stuff is accessible in the latest build which you can download from here

P.P.S. You can read this post in Russian here