Voting

in your post that this should be ootgrhonal from a compiler perspective but I'm not sure how it can be). Yours is a simple case, but I could see this type of thing getting out of control for more complex cases. Other developers would have to accept your view and program accordingly. In other words, extending any language via macros or macro-like constructs is a catch 22 situation.Brings me back to the days using assembler and people having their own toolkits of macros. They were usefull and all but they almost always degenerated into their own minilanguages and impacted development and maintenance.It seems that the purpose of any source language(with all it's shortcomings) is to provide a baseline grammar and syntax to allow everyone to communicate with. If you go down the path of You say POTAYTO, I say POTAHTO with source view representations, it's only going to cause confusion in the long run.Anyway, I'll still use your plugin if you post it