Tim Jansen's blog

I did almost no work in the Eek spec in the last two months, but I hope to finish it this year anyway. I took almost the whole december off, so I should have enough time for that. The last time I wrote about generics, I underestimated the problem. Java has a huge generics FAQ for a reason. Eek needs either C++-like template methods or Java-like wildcards. I prefer Wildcard with a C++-like template syntax, but I don't know the details yet. However, my main challenge became bigger by the addition of generics: to create a coherent model for delegates. Delegates must support generics, as well as all features of methods like overloading and dynamic dispatching/multi-methods. It must be possible to create delegates either from a class's methods, or with a closure. And a method should only syntactic sugar for a property that contains a delegate. With some kind of circular dependency, because a property can have getters and setters methods, which are delegates themselves. It will take some time to sort this mess out, but then the rest should be easy.


This blog is my dumping ground for thoughts and ideas about Eek. Someday Eek will be a programming language and system, somewhat comparable to Java in scope. It is my attempt to bring sanity to the world of computing.
At least I hope so. Right now it is far from being finished and I can't guarantee that it ever will be. I am still working on the specification, but I won't release anything before I got my first prototype running. The world does not need more vapourware and unusable beta-software. All publicly available information about Eek is contained in this blog. You can find the latest summary here.
This page is powered by Blogger. Isn't yours? Creative Commons License
This work is licensed under a Creative Commons License.