>>Still more serious it is to release a new product, like VFP9,
>>without the DETAILED list of all the fixed bugs.
>>
>>Every correct bug can change the behavior of the application.
>>
>>I still do not have an application much extending,
>>But without a list of the made variations,
>>I would be paralyzed from the idea to use a new package
>>of which I cannot know the modifications.
>
>Please refer to the KB articles below...
>
>Miscellaneous problems that are fixed by Visual FoxPro 9.0
>
http://support.microsoft.com/kb/894011/EN-US/>
>Memory leak and corruption bugs that are fixed in Visual FoxPro 9.0
>
http://support.microsoft.com/kb/894010/EN-US/Ken,
You have replied to Fabio, but not to me (
Re: VFP Bug list seems to dry up Thread #
989551 Message #
991406). My question is different but related, so I take the freedom to jump in here and ask you again:
Where should we go when we want a (full) list of known, but yet unresolved, bugs?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
