An Ioke update


I haven’t written here in a while – the reason being that I’ve been seriously heads down with Ioke, having a blast implementing new things and planning the future. I’m happy to have received several contributions from other people. Github makes this so easy it’s silly.

Since December 23rd – when Ioke 0 was released – I have made quite a lot of changes to Ioke. The highlights are these:

  • fixed all outstanding bugs reported
  • several examples, contributed by Carlos Villela
  • Range#each
  • ensure (like Ruby ensure, Java finally)
  • lexical macros
  • become!
  • full implementation of Regexp and Regexp Match
  • freeze!, thaw!
  • case expression
  • list comprehensions, set comprehensions and dict comprehensions
  • support for TextMate
  • alternative syntax for text and regexps
  • interpolation inside of regexps
  • support for syntactic macros
  • support for quoting and metaquoting
  • cond expression
  • destructuring macros
  • added support for inverted ranges
  • added methods to remove cells
  • added methods to find the owner of cells

So as you can see, I’ve been kinda busy. Ioke has garnered some real attention too, which is great fun. The github repository has over a 100 watchers. The guide has been viewed over 3500 times. The distribution packages have been downloaded about 400 times.

But right now I’m looking to the future. There are still many, many small holes in the core libraries, but with regards to the big stuff there is basically three pieces missing. These are Java integration, aspects and concurrency. I haven’t started on any of these because I haven’t decided exactly how they should look like. Especially the concurrency issue is definitely problematic. So I’m punting on it right now. But I promise to have an answer within a few weeks to these three major issues.

So what’s the plan? Ioke S will be released within 2 weeks. The guide need to be updated quite substantially, since all the features I listed above need to be described, and some of them are really complicated. They are very nice of course. I will also create at least a few more examples to show some actual code. I might write about it here to show some features.


3 Comments, Comment or Ping

  1. George Anderson

    Consider dropping a link or two into these update posts (e.g. to ioke.org or the github repo) to facilitate easier exploration for the uninitiated. I see links in your sidebar, but some of us just read the feed.

    Thanks for sharing,

    /g

    January 6th, 2009

  2. George: if your browser’s working properly, there’s a link to Ioke’s site on the right of the page. (OK, you probably knew that.)

    January 6th, 2009

  3. Hooray for the new features, and thanks for the new examples.

    January 7th, 2009

Reply to “An Ioke update”