On Nov 8, 2006, at 12:19 PM, Gregory Brown wrote: > I just got done with some Ruport based $work and I realized something. > > I really like the way Table/Records work!
Then there's not really any need to change them. I just don't see what Records get me that I don't get from a plain Hash. > This stinks of badness, especially when i think... what if I want > > table[0][0] . > > Can't do it if we use raw Hashes instead of a Record > I'd need to do > > table.row_array[0][0] or something ugly like that. You're right, that would be ugly. Is that a common need for you? I haven't needed that yet. > Can someone remind me of the good reasons for getting rid of Records > though? I'm seriously asking, because I forget if there was an Aha! > moment that made it all make sense. I think it was more that we couldn't come up with any good reasons for _keeping_ Records. But if you feel strongly about it, then keep them. I'll bring it up again later when I have more time for coherent arguments ;-) > On a second glance, it looks like we're complicating table to possibly > fix something that's not broken. Table does become more complicated, but I think losing Record still nets out to a gain in overall simplicity. :dudley _______________________________________________ Ruport mailing list [email protected] http://lists.stonecode.org/listinfo.cgi/ruport-stonecode.org
