Bug 4338 - Improve error message that confuses our users
Summary: Improve error message that confuses our users
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2012-04-08 14:02 UTC by Miguel de Icaza [MSFT]
Modified: 2012-04-10 07:34 UTC (History)
1 user (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 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:

Description Miguel de Icaza [MSFT] 2012-04-08 14:02:10 UTC
The following pattern happens in MonoTouch:

class X { 
   static int Foo { get { return 1; }} 

   static void Main () { Foo (1); } 

Here, instead of reporting something like "You are trying to call Foo as a method, but it is a property", we report;

/tmp/x.cs(6,17): error CS0122: `X.Foo' is inaccessible due to its protection level
/tmp/x.cs(6,17): error CS1955: The member `X.Foo' cannot be used as method or delegate

People get confused about the first 0122, even if we later provide 1955
Comment 1 Marek Safar 2012-04-08 17:47:06 UTC
It looks like you are running some old mcs, I tried it with master and I get

x.cs(1,69): error CS0103: The name `Foo' does not exist in the current context

It's not ideal (will try to improve it) but much better than reported
Comment 2 Marek Safar 2012-04-10 07:34:46 UTC
Fixed in master.