For an upcoming project of mine, I need to extend a piece of code I have written to allow it to manage "nested" versions of itself. I've decided that the best way to do this is to change the storage of data from row/column representation to a hash-like representation (with some extra plumbing to manage the new form, of course). What I don't know yet is whether XML or Storable will be the better solution to use.
First off, I'll have to confess: I'm not exactly an XML pro, and I am a bit partial to Storable. I'm very familiar with Storable, and know exactly how to approach the problem with it. However, at the back of my mind, that I've been wanting to take a look at XML at see if it is worth the hype. Does anyone have any opinions on the advantages/disadvantages on either?
In reply to XML or Storable? by jryan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |