RE: NO!!!!
>> This library is incompatible with earlier versions.
>So? No one promised compatibility, in fact, until v1.0 we are >warning
>people
>that there are going to be minimal attempts to be backward >compatibile.
>We
>won't try to be incompatible, but if a better way is discovered to do
>something, then it might be put in even if it will "break" existing
>>code.
Of course the simple solution would be to provide past versions
for download as well as the current version.
This means NO code really gets broken.
For example:
winlibV001.ew comes out and someone writes program01.exw
then later:
winlibV002.ew comes out, someone downloads program01.exw and
downloads winlibV002 and program01.exw no longer runs without
crashing.
If there was a note in program01.exw declaring the winlib version
it was written for, and that same version was still available on
the web, program01.exw would always be able to run because they
could download the version it required.
Granted it takes a little more web space, but thats life.
Zipped text files are often much smaller anyway.
If patch program updates are used, they may not be as reliable
unless they can somehow be tested really good, but that may
introduce another bug testing phase into the works also.
Note that in several open source projects this is
exactly the way it is handled. Its also known that some programmers
have a preference for older library versions also, while they wait
for bugs in new versions to be fixed or whatever, or they simply
'like' using the older version that they had built several
routines for and dont want to wade through thousands of lines of code
in order to update their (previously working) program to the new
standard.
In the meantime, i strongly recommend anyone building a program
or library around winlib to include the winlib version they used
in the zip along with their program in order to assure the user
gets the correct version.
This should help some...
Good luck with it.
--Al
|
Not Categorized, Please Help
|
|
