Bug 34841 - LINQ expression Implementation issue
Summary: LINQ expression Implementation issue
Alias: None
Product: iOS
Classification: Xamarin
Component: BCL Class Libraries ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-10-13 17:43 UTC by Brad Herzberg
Modified: 2016-06-09 13:53 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Brad Herzberg 2015-10-13 17:43:53 UTC
Occurs when using the Parse option to evaluate a math expression utilizing division.   If the result of the equation is between 1 and 0 the function below will always return 0 rather than the actual value.  (e.g. "5 / 25" will return 0 rather than 0.2).    This method works as expected using .NET.

return double.Parse((string)row["expression"]);

Below is the full code snippet:

            DataTable table = new DataTable();
            table.Columns.Add("expression", typeof(string), expression);
            DataRow row = table.NewRow();
	    return double.Parse((string)row["expression"]);
Comment 1 Sebastien Pouliot 2015-10-13 18:52:43 UTC
From your description it is not clear where the problem is. The above snipped has no LINQ usage and could have issues with the current culture of the device (or simulator) while parsing the result.

Please attach a self-contained test case and include all the version* information.

* The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
Comment 2 Sebastien Pouliot 2016-06-09 13:53:03 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!