<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Am 11.06.2013 um 09:27 schrieb Henri Verbeet:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">We always want to use '.' as decimal separator in GLSL, instead of the locale<br>specific one. Reported on IRC.<br></span></blockquote></div>I think this should be added as a code comment above shader_glsl_ftoa, I don't think the reason why we need our own conversion function is obvious.<div><br></div><div>The ARB shader backend will need this as well, but I can take care of this. What external software triggers this behavior?</div><div><br></div>> case WINED3D_DATA_FLOAT:<br>> - sprintf(register_name, "%.8e", *(const float *)reg->immconst_data);<br>> + shader_glsl_ftoa(*(const float *)reg->immconst_data, register_name);<br>> break;<br><div>shader_glsl_ftoa doesn't handle inf or nan. I assume that's intentional because they would only trigger a parser error.</div><div><br></div></body></html>