I'm not sure you realize the can of worms you would be opening up by feeing up the syntax chain. I agree freeing up syntax is a very viable method for imporving codeing, but it is also very easily leads twards confusion in the minds of code maintainers. The idea is old and has been implemented a number of times, but also it has never taken off because of the major problem with what does "for (x) in Y {;;some more code here}" mean? FYI, I've implemented a flexible programming language. They are a bear to implement. I'm positive you don't want to go there. Think about this. The developer tweeks the syntax translation for the code he is working on. What happes to all the other uses of that syntax in the program?