[ioke-dev] Re: Data structure melee

[Ola Bini <ola.bini@gmail.com>]

Kosta Welke wrote:
> On Thu, 29 Jan 2009 13:43:00 +0100, Ola Bini <ola.bini@gmail.com> wrote:
>
> > So, as you know, I've been trying to find a good data structure to 
> > use for representations of cells in Ioke. This mail will first detail 
> > the problem/requirements, and then talk about my current ideas.
> > Ideas, thoughts?
>
> I suppose you know Steve Yegges "Universal Design Pattern" blog entry? 
> It exactly about that problem. He also uses Java to implement a 
> protype language.
>
> http://steve-yegge.blogspot.com/2008/10/universal-design-pattern.html
>
> Short version: Use a an array up to a certain size, then a hashtable 
> or a tree.
>
> If you cache mimic cells that means you need some way to mark their 
> children dirty, which means objects have a list of objects that mimic 
> them. But it speeds up peformance.
>
> I hope my summary is correct, I read it some time ago.
>
> Kosta
I'm sorry, but that isn't the problem. His recommendation of data 
structures doesn't take inheritance into account. Take a look at the 
current structure in my mail again to see why. Steve mostly doesn't talk 
about this problem.

Cheers

--
Ola Bini (http://olabini.com) 
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)

"Yields falsehood when quined" yields falsehood when quined.