Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@d4ng3r0u5 probably since it depends on the culture settings.
in my case float.Parse("1.6") is 1.6 and float.Parse("1,6") is 16, on a vm i have it's the opposite,i solved by setting the thread culture to InvariantCulture, but before parsing new files i'll always replace commas with dots to be safe
How do you even come up with shit like this?
I found such a treasure today in the production code.
Just wasted two hours because C# float.parse only allows dots for decimal places and ignores commas..... But float.tostring uses a comma WTF.
I was writing an obj file exporting the vertices with tostring, then when loading the model would show up broken but in other 3d applications it worked.
Who did come up this bright idea ?
rant
c#
floating points