> it is fine to have them unversioned if they are in an
> application local
> directory. However if they live in a centralized directory
> they should have
> version embedded - if they don't you end up withh DLL at every update.
> ".so" files are a little easier to use as you can easily have multiple
> versions on filesystem.
>
at the cost of making it harder to simply upgrade. That is, 1.4.2 is
supposed to be a drop in replacement for 1.4.1, and both are upward
compatible with 1.3.x. Now, if you get to the point where 2.x is no longer
compatible with 1.x, either up down or sideways, I believe the right answer
is a new name.
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named. Any use, copying or disclosure by any other person is strictly
prohibited. If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
