On Thu, Feb 27, 2014 at 11:32 AM, Max Leske <[email protected]> wrote:
> > On 27.02.2014, at 14:54, Mariano Martinez Peck <[email protected]> > wrote: > > > > > On Thu, Feb 27, 2014 at 10:48 AM, Lorenzo Baracchi < > [email protected]> wrote: > >> Hi >> >> I was using FLMaterializer materializationFromFileNamed: filename to read >> fuel files. >> Until yesterday everything was fine, but today I updated Pharo and >> received the error "'Materialization error. Unexpected stream version 19 >> where it should be 193." >> >> I guess that a new version of fuel cannot (simply) read old versions >> files. >> > > This is the "default" exception. But maybe....between 1.9 and 1.9.2 the > file format didn't change. Max? > > > I think 1.9 to 1.9.3 should work without problems. I can't think of any > changes to the file format. > > An interesting idea for Fuel would be that for each released version, besides defining the version, we also define the list of previous versions that are known to work with this one. So for example, we could say that 1.9.3 should work ok up to 1.9. So upon materialization we check this info. This would be very cool. Of course, it is our responsibility (humans/developers) to define with which previous versions it should work... Best, > > >> Is there a way to know in which version of fuel a file was written and >> use that version to read it? >> > > In the exception message itself. "'Materialization error. Unexpected > stream version 19 where it should be 193." > It says that in the current stream the version is 19 but the code now > expects 193. So you should load Fuel 1.9 to materialize those files. > > Best, > > > >> >> thanks >> Lorenzo >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com
