Mariano, I gave you a pretty tough time :) It appears that you understand that I did so with the best of intentions. Thanks for listening.
One problem that I do *not* think you need to solve is that of old software talking to new software. Someone wanting forward compatibility is probably going to use XML or something similar to get a timeless protocol that will be of necessity very simple. A good serializer is hard to write, and forward-compatibility is probably too much to ask, particularly when efficiency is a stated goal. A backwardly-compatible Fuel will be most welcome and useful. Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Mariano Martinez Peck [[email protected]] Sent: Thursday, October 20, 2011 7:00 AM To: [email protected] Subject: Re: [Pharo-project] When will Fuel file format stabilize? On Thu, Oct 20, 2011 at 12:54 PM, Ben Coman <[email protected]<mailto:[email protected]>> wrote: Mariano Martinez Peck wrote: Well...thanks guys. The point is taken. Thanks Philip, Bill and all who gave feedback and suggestions. We are aware of this and we are already discussing with Martin possible solutions and analyzing all the things that has been said in this thread. We will keep you informed. Cheers Just one thing I hadn't seen discussed. Is Fuel possibly a way to exchange objects/data between users/systems ? Yes In which case it would have to deal with different systems having different versions of Fuel. Exactly. It doesn't matter whether the different versions of Fuel happens in your own image or in different systems. So yes, it is the same problem. Note this is not only a problem for Fuel, but for any serializer which does not manages full backward compatibility between versions. -- Mariano http://marianopeck.wordpress.com
