Floating point type parameters parsing problem

[RuslanMarchenko]

When I call odata function with a double parameter, I can see that ExpressionLexer.MakeBestGuessOnNoSuffixStr method is using current thread culture for several TryParse method calls when trying to parse the parameter from the url. I suppose that to be a bug because the numeric literal format is fixed in OData-ABNF, the double one for example. It seems that there is a need to call TryParse with invariant culture, insn’t it?

[congysu]

@Ruslan: Would you like to contribute a fix for the issue? Thanks.

[cisnetsov]

Same problem. Any update?

[maximpashuk]

If CurrentCulture is russian (for example), then double.Parse("0.23") will fail and double.Parse("0,23") will success - used comma instead of dot.
Because ABNF for ODATA resticted to dots, so ExpressionLexer should use InvariantCulture then parsing strings.
I made in in my pull request #374

[lewischeng-ms]

PR #374 has been merged. @maximpashuk Thanks for your contribution again!