[Mono-bugs] [Bug 31846][Wis] New - error order reporting could be improved

[bugzilla-daemon@rocky.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by vladimir@pobox.com.

http://bugzilla.ximian.com/show_bug.cgi?id=31846

--- shadow/31846	Sun Oct  6 21:08:54 2002
+++ shadow/31846.tmp.3606	Sun Oct  6 21:08:54 2002
@@ -0,0 +1,47 @@
+Bug#: 31846
+Product: Mono/MCS
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: vladimir@pobox.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: error order reporting could be improved
+
+(marking this as wishlist, but is fairly annoying)
+
+Currently mcs seems to report errors "as they occur" as the trees are being
+walked internally.  This leads to error reports like:
+
+SqliteDbCommand.cs(153) error CS0103: The name `behaviour' could not be
+found in `System.Data.SqliteClient.SqliteDbCommand'
+SqliteDbCommand.cs(169) error CS0117:
+`System.Data.SqliteClient.SqliteDataReader' does not contain a definition
+for `SqliteCallabck'
+SqliteDbCommand.cs(172) error CS0165: Use of unassigned local variable `err'
+SqliteDbCommand.cs(175) error CS0165: Use of unassigned local variable
+`rows_affected'
+SqliteDbCommand.cs(159) error CS0177: The out parameter `rows_affected'
+must be assigned before control leave the current method.
+SqliteDbCommand.cs(64) error CS0029: Cannot convert implicitly from
+`System.Data.IDbConnection' to `System.Data.SqliteClient.SqliteDbConnection'
+SqliteDbCommand.cs(7) error CS0536:
+`System.Data.SqliteClient.SqliteDbCommand' does not implement interface
+member `System.Data.IDbCommand.CreateParameter'.  (method might be private
+or static)
+SqliteDbCommand.cs(7) error CS0536:
+`System.Data.SqliteClient.SqliteDbCommand' does not implement interface
+member `System.IDisposable.Dispose'
+
+Note that the error line numbers bounce all over the place (although with a
+general downwards -- "backwards" -- trend in each error category/parsing
+pass I assume).  It would be very useful to have this sorted by line
+number, low numbers first, at least as far as fixing errors goes.