Extensible Term Language 0.2.1 Released

I have released ETL 0.2.1, the hardest part was writing the tutorial. The language specification is not yet here yet, but I see how to tackle it.

The tutorial experience was quite interesting. I have made a lot of fixes to the language in the places where it was simpler to fix than to explain. Some bugs were detected in the areas that are not covered by the test suit. Also I have added new features to avoid some lame excuses in the tutorial. I guess I will continue writing tutorials.

This makes me wonder if the developers should write at least documentation drafts for their products. The attempt to explain product to the user could seriously affect the product interface and the product features. If it is hard to explain, possibly it will be hard to use as well. Possibly aversion to writing the documentation is caused by the desire to avoid realization that the code has a questionable usability and quality. The usable product should have a working model that is easy to explain.

AsyncObjects 0.1.0 finally out

After long time and some pain I have released an updated version of the the AsyncObjects framework.

The frameworks has been worked upon mostly in the context of the Sebyla project. It is a blatant rip off of ideas of E programming language. Initially, it was created just as prototype of some ideas for the Sebyla project back at 2002. And I have tried some new ideas in it form time to time. I have even ported the thing to Java 5, and I have learned in process how thin the layer of generics in Java is.

For some weird reason, nothing similar had appeared during five years of the framework life.

Then there was a project that might have used the framework. However it would have used the framework on Foundation Profile 1.1 runtime. So I partially took old version and and partially removed generics from new version and I have put into the separate project that is currently the home of the framework. Alas the project has been canceled just after the beginning. However I have done some work on the framework in context of that project. After that I have continued the work in my free time. However the framework was a low priority project for me, so the progress was glacially slow. There is a higher priority personal project.

Now there is yet another project that might use the framework. And it already has a dependency on Java 5. The framework might experience yet another flip, now to Java 5. If this project won't happen, I guess I would need to advertise it on some wider forums.