Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to read SP2 Fix List?
Message
From
22/12/2007 20:32:35
 
 
To
22/12/2007 17:42:04
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows XP
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01277191
Message ID:
01277199
Views:
18
>The SP2 downloads include a document named "List of Fixes in Visual FoxPro 9.0 Service Pack 2".
>
>There are items that start out with "VFP6", "VFP7", etc.
>
>What are these?... Does it mean that the bug was first reported in the named release and now fixed in SP2 or does it mean that they are issues fixed in the release named?

AFAIK it describes the version the error can be first reproduced in. Perhaps I have the largest spread of versions of reported bugs: the LL file bug open/seek was introduced in vfp9Sp1, whereas the error in "index ... for [long clause]" had been in foxpro for ages already and I stumbled on it using a generator in vfp9. The rushmored non-use of vfp functions I described to Aleksey here on UT many months ago is also in the fixed list - I was sure I had once tested and found it to be working and this fixed again as well. IIRC this one was introduced in vfp7 (which I had skipped).

IMHO from bugs known to be *introduced* by SP2 I am worried mostly about Cathy's report bug. But there are some doozies in the fixed list as well... For me the question is mostly "How much risk is there that I will encounter *this* bug" coupled with "how many lines needed to work around it". Remember the nasty possibility of vfp loosing the alias if an identical alias had previously be closed ? This was an error cropping up once in a couple of million "use", but it bit me a couple of times - but I had it controlled via lots of code logging and analyzing it, as it was *not* reproducible at will. Just something you had to guard against. Nowadays this code lives only in source safe, as this was fixed, but when the bug was "threatening", most of the apps I read were wide open and if they encountered itm it was so seldom nobody could find the pattern.

regards
Previous
Reply
Map
View

Click here to load this message in the networking platform