I’m a foundations guy. The thread that unifies all my interests in life is “fixing the foundations”, or more accurately and with less alliteration, “improving the foundations of the world”. Here are some of the things I have in mind.
The Common Subexpression Problem
This is my response to “Why I Don’t Use a Parser Generator”.
A while ago I removed the
# that LES/EC# adds at the beginning of all operator names. Having written quite a few macros now, I am starting to think that was sort-of a mistake. The reasons for removing it seemed good, but one of the reasons turned out to be kind of bogus.
After living on CodeProject for a couple of years, it’s past time to unveil the new LLLPG home page.
I’d like to make a “universal” programming language that takes the best features of all the new languages, and either (1) directly supports those features, somehow, or (2) provides lower-level primitives out of which those features can be built, with features provided by the standard library.
I proposed Loyc Expression Syntax version 1 to an external group for the first time recently, and did not get a warm reception. ‘Non-obvious whitespace rules’, ‘overbearing semicolon requirements’, and ‘operator precedence rules that differ from C/JS’ were mentioned as pain points. For two weeks I thought and I thought, exploring different options, and while I could not find a perfect solution, I did find a solution that I am happy with.