General information
Category:
Visual FoxPro Beta
Hi Marvin,
It's a situation that 'most' of us simply have learned to accept, some of us most grudgingly.
I blame the bug reporting mechanism as much as anything... it's a black hole and if your bug is not reproducible as supplied (and many are not because they often have unobvious related factors) immediate it is dropped without notification of any kind!
On the other hand most of us, the longer we use the language, become forgiving because it is otherwise sooooo useful.
regards
Jim
>Hi!
>
>Did somebody check wether the old bugs are yet solved? Thinking of getting rid of this by changing the language.
>
>Still thinking of this for example:
>a= -1
>b= -0.1
>c= 1
>d= 0.1
>x= a+b+c+d
>? empty(x) &&Gives me a .f. because of a floating point error on 34 commavalue
>? empty(-1-0.1+1+0.1) &&While this gives me a .t.
>
>I think first of all Microsoft should solve ALL the previously posted errors. Or can they tell me how to sell my Sodftware to customers when they receive errors nobody will solve...
>
>(I am kind of getting angry the longer I use Foxpro)
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only