[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 Kenji Hara changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 --- Comment #10 from Andrej Mitrovic 2013-06-01 08:21:02 PDT --- (In reply to comment #9) > Therefore, I can say that the root cause was exists in the mis-operation for > building and packaging release files. I figured that might be the prob

[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 Kenji Hara changed: What|Removed |Added Keywords||wrong-code --- Comment #9 from Kenji Har

[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 --- Comment #8 from rswhi...@googlemail.com 2013-05-31 03:27:14 PDT --- Does anyone knows in the meanwhile, which commit solved the problem? The workaround is to use enum but it would be nice if const would work in dmd 2.063... -- Configure i

[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 --- Comment #7 from Tiberiu Gal 2013-05-31 01:17:04 PDT --- it's not about calculations, it's about accessing const fields in classes and structs. it works perfectly with local variables, it works when accessing the them from within the clas

[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 Tiberiu Gal changed: What|Removed |Added CC||galtibe...@gmail.com --- Comment #6 fro

[Issue 10215] Regression (2.063 release): const causes wrong float calculation

http://d.puremagic.com/issues/show_bug.cgi?id=10215 Andrej Mitrovic changed: What|Removed |Added Summary|const causes false float|Regression (2.063 release):