> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Bryce Yancey > Sent: Saturday, August 07, 2004 11:09 AM > To: [EMAIL PROTECTED] > Subject: RE: Critical problem in new format (was: Support for new > Plucker features in the Parser.) > > > This will, however, make the new format non-backwards compatible. > > Bummer. If it's not possible to make these changes completely backward > compatible, do we want to consider changing the plucker format version > number (currently 2)? That way old readers would presumably report the > book as incompatible rather than corrupt...which would be a little less > confusing to end users.
I was thinking of something like that as well. This would be a major change to Plucker, deserving of a major version number increase. And users are more likely to accept major changes in a version upgrade like that. Major changes are *expected*. Simply make it as clear as possible up front that older versions of the reader won't be able to read the new documents. As long as new builds of the reader can still read *old* documents you won't have insupperable problems. > Yep. If the format must change, it would be good to add some way to > better allow for future changes without breaking the format. Hmmm. Stick as much info as possible in the header describing every bit of the document structure, so future extensions basically change some pointers about where in the file things are? ______ Dennis _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
