Bug 30527 - Is operator failing in expression
Summary: Is operator failing in expression
Status: RESOLVED FIXED
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: 4.0.0
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2015-05-28 00:43 UTC by vijay
Modified: 2015-05-29 01:47 UTC (History)
2 users (show)

Tags:
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 GitHub or Developer Community 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:
Status:
RESOLVED FIXED

Description vijay 2015-05-28 00:43:24 UTC
Hi,

Is operator failing to handle expression. Attached sample test give more detail on failing test.
Comment 1 Marek Safar 2015-05-28 03:16:54 UTC
Could you attach the failing test?
Comment 2 vijay 2015-05-28 05:36:35 UTC
Attached programme it self have test.If you run this programme it will never come out from condition if (df1 != null).

I have just went to alternative solution,which will not use "Is" operator but do the same job.

  try
  {
      if (!(df1.GetType() == typeof(DataFrame)) || !(df2.GetType() ==   typeof(DataFrame))) return false;
  }
  catch(NullReferenceException nullException)
  {
    return false;
  }
Comment 3 Marek Safar 2015-05-28 05:42:08 UTC
Fixed in master/4bfbc0c75b72c057eb5eacc904910b15e49067a1
Comment 4 vijay 2015-05-29 00:37:57 UTC
I couldn't able to trace commit in Mono/Master.Could you please send me direct link so that i can test.

I was looking at https://github.com/mono/mono/commits/master/