i agree with Stef.. about method metadata. imo array literals is more than enough to encode any data. yes, it may require a separate layer to convert it into instances of other classes ,like Dictionary, Author, Timestamp, PreviousVersionLink (+ add what you desire). So, you basically need to write a parser (or decoder) of array data. Which is imo much more simpler than parsing textual representation like JSON, STON and even smalltalk syntax.
But lets stop fighting. Nothing is better a working solution, even if it not flawless. I would just use fuel to serialize any additional data associated with method. With some version information, so that i can make sure that i will be able to read it 10 years later. I don't care that humans will not be able to read it, because we have tools for that. End of story. -- Best regards, Igor Stasenko.
