Bug 4709 - C# REPL displays last error continuously after wrong using
Summary: C# REPL displays last error continuously after wrong using
Status: RESOLVED FIXED
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: Other Other
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2012-04-28 08:29 UTC by Konrad Kruczyński
Modified: 2012-05-18 06:36 UTC (History)
2 users (show)

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


Attachments
Screenshot with a sample of the problem (36.77 KB, image/png)
2012-04-28 08:29 UTC, Konrad Kruczyński
Details


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 Konrad Kruczyński 2012-04-28 08:29:55 UTC
Created attachment 1771 [details]
Screenshot with a sample of the problem

Description of Problem:
When using C# REPL, if one enters bad (i.e. nonexistent) namespace in using declaration, the REPL produces the correct error. Nevertheless all actions done after that ends with such error, quit included.

Steps to reproduce the problem:
1. Run csharp.
2. Enter using System.Liqn; (for instance)
3. Try to do anything else.


Actual Results:
The error about bad using is report continuously and no actions are done.

Expected Results:
Proper reaction to the statements.


How often does this happen? 
Always.


Additional Information:
This is on fresh trunk, precisely version 2.11.2 (master/328fb47). The attached screenshot illustrates the problem.
Comment 1 Atsushi Eno 2012-05-14 03:12:28 UTC
Another aspect of this problem:

$ using System.Xml.Linq;
(1,19): error CS0234: The type or namespace name `Linq' does not exist in the namespace `System.Xml'. Are you missing an assembly reference?
$ help
(1,2): warning CS0105: The using directive for `System' appeared previously in this namespace
(1,19): error CS0234: The type or namespace name `Linq' does not exist in the namespace `System.Xml'. Are you missing an assembly reference?
csharp> ?                      
(1,1): error CS1525: Unexpected symbol `?'
csharp> quit
(1,2): warning CS0105: The using directive for `System' appeared previously in this namespace
(1,19): error CS0234: The type or namespace name `Linq' does not exist in the namespace `System.Xml'. Are you missing an assembly reference?

I couldn't even quit until I type below:

csharp> namespace System.Xml.Linq {}
(1,2): warning CS0105: The using directive for `System' appeared previously in this namespace
Comment 2 Marek Safar 2012-05-18 06:36:07 UTC
Fixed in master