|
|
Post by DJLinux on Dec 22, 2008 22:17:03 GMT -5
var#=vec3(0.0.5,0.4,0)
without an error or warning it's hard to find the source of error in larger complex code
Joshy
|
|
|
|
Post by dw817 on Apr 17, 2009 12:58:46 GMT -5
Actually, it's worse than that. This is also acceptable.
print 0.0.5
Results are:
00.5
Freaky !
|
|
|
|
Post by UNDISCLOSED on Apr 26, 2009 4:34:38 GMT -5
I dont get that at all, if B4GL does not see the error it should at least crash or something..
|
|
|
|
Post by dw817 on Apr 26, 2009 10:32:58 GMT -5
Hi Wolfman & DJLinux:
* I suspect Tom had not anticipated someone entering two decimals for a constant or calculation. As near as I can tell, it is treating one of them as semicolons. It's not very serious; only affects appearance, and can be easily fixed.
|
|
|
|
Post by UNDISCLOSED on Apr 26, 2009 10:42:17 GMT -5
1- It may be purposefull
2- it is quite sirious if you accidentaly add in an extra decimal and then cant find out why your sprite is bright orange instead of blue!
|
|
|
|
Post by Darkjester on Apr 26, 2009 12:20:35 GMT -5
might have something to do with the way tom did the floating point stuff, any ideas when either a) djlinux's compiler is done for basic4gl.. or b)new basic4gl release
|
|
|
|
Post by dw817 on Apr 29, 2009 8:30:44 GMT -5
Well, now that a serious bug has been nailed down, does anyone know how to find TOM ?  |
|
|
|
Post by UNDISCLOSED on Apr 29, 2009 11:10:23 GMT -5
I E-Mailed him once and he replied.
|
|
