[M3devel] <*LAZYALIGN*>

[Mika Nystrom]

Ugh!!!  I am still using compilers that are almost ten years old
on ALL my systems just because I need to share pickles between them
and CM3 has a different TEXT format from my ancient PM3.  Tony
thinks there's a workaround with specials but I haven't had a chance
to get to it yet...

    
"Randy Coleburn" writes:
>This is a MIME message. If you are reading this text, you may want to 
>consider changing to a mail reader or gateway that understands how to 
>properly handle MIME multipart messages.
>
>--=__Part6F499F9A.2__=
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: quoted-printable
>
>Sorry, but I've never checked to see how pickles represent "BITS FOR".
>I've used BITS FOR only on rare occasion.
>=20
>My concern about "breaking" is that if a change is made to the encoding of =
>pickles, then all other programs that use pickles would need to be rebuilt =
>in order to remain compatible.  I seem to recall that there is a version =
>number that is put into the encoding to help with compatibility and of =
>course we already have pickle, pickle2, netobj, and netobj2.  Perhaps your =
>change could be structured in such a way as to still understand the older =
>variants for compatibility.
>=20
>Here is a scenario:  Suppose I have a program that uses pickles and/or =
>netobj.  A version is built and put into an embedded system.  This system =
>shares pickles/netobj with another client program.  After the embedded =
>system is fielded, a change is made to the encoding of pickles.  New =
>features are added to the client program and it is rebuilt.  Now the =
>client program can't share pickles with the embedded system.
>=20
>Scenario2:  A program uses pickles to store data in files.  If the pickle =
>structure is changed, the program will no longer be able to read its old =
>files without some sort of transformation function on all the files.
>=20
>Regards,
>Randy