News

While the news section gives a somewhat approximate view of Scalpel's development progress, the mailing lists and the source code itself may need some deciphering.

The new feature matrix is a good compromise. It provides a both detailed and accessible summary of the current implemented features.

The contributor documentation is finally online! You'll be able to know everything about the current Scalpel design.

I've also decided to share with you my expectations for the future of Scalpel. See the new introduction and long-term goal pages.

Two mailing lists (scalpel-dev and scalpel-users) and an IRC channel have been set up for the community.

I've migrated the Git repository from BerliOS to GitHub, which provides a sexier bug tracking system and a better interface to Git.

As you may notice, there hasn't been any new revision since a couple months. Even if I don't have as much time as before to give to the project, I certainly don't want it to die. Scalpel isn't usable yet, but it's a fairly advanced work in progress.

This is why I believe it's time to open the project to the community. I want to encourage as many competent people as possible to contribute to it.

Yesterday I ran the Standard Library Test (which consists in analyzing a C++ standard library implementation with Scalpel) for the first time since a couple of months. I didn't have any particular reason to do this as I didn't change the syntax analysis related source code, but I did it anyway. It's sometimes good to be overcautious!

As those who keep watching the demo page may already know, Scalpel's semantic analyzer has made great strides since the previous news article.

It's now able to perform semantic analysis of:

• namespace definitions
• class declarations
• global and member variable declarations
• free and member function declarations, including constructors, destructors, operator functions and conversion functions
• function parameters, including unnamed ones
• class inheritance

Want to catch a glimpse of the current capabilities of Scalpel without having to download, build and configure it? Then you should have a look at the brand new "Demo" page. It's kinda short for the moment but this is only the beginning. Besides, it could give you an idea of the amount of work that has been done.

Stay tuned!

Finally, after almost one year of work, I'm proud to introduce to you the Scalpel project!

Well, it isn't complete yet, nor it is usable, but we're pretty close to the goal.

I recently reached a symbolic step: Scalpel passes the C++ standard library syntax analysis test! This test consists to analyze the source code, generate a syntax tree, regenerate a source code from it and then check whether the original source code matches the generated one. So, Scalpel is now able to generate a correct syntax tree of the whole C++ standard library implementation of GCC 4.4.0.