Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!cbosgd!osu-cis!apr!whp
From: whp@apr.UUCP (Wayne Pollock)
Newsgroups: comp.sys.mac
Subject: Re: LSC bug?
Message-ID: <280@apr.UUCP>
Date: Sat, 26-Sep-87 20:41:34 EDT
Article-I.D.: apr.280
Posted: Sat Sep 26 20:41:34 1987
Date-Received: Sun, 27-Sep-87 12:05:23 EDT
References: <3320019@hpcid.HP.COM> <2864@husc6.UUCP> <2867@husc6.UUCP> <2868@husc6.UUCP>
Reply-To: whp@apr.UUCP (Wayne Pollock)
Organization: APR, Columbus, OH
Lines: 14
Keywords: time, LSC, libraries, bug
Summary: Make it an option.

Whenever a product changes functionality, you have this problem.  For software,
a reasonable approach is to add a menu choice (which is remembered until reset)
called something like "version 2.01 compatibility mode".  Add plenty of clear
documentation about the differences, and encourage everyone to not use the
feature, as it will be dropped in future releases.  And several updates later,
you can drop the feature.
This is reasonable because software usually has a live span measured in a small
number of years; allowing people to compile old software for a while is ok, and
sooner or later it will be rewritten (you should provide help for this, perhaps
supplying new routines that work the way the old ones did), or it will be dis-
carded.
By the way, just what is the current release of LSC?  The latest version I have
is 2.01, do I need to upgrade?
Wayne Pollock,	...!{inhp4, cbatt}!cbosgd!osu-cis!apr!whp