[Mono-bugs] [Bug 82444][Nor] Changed - mcs reports different char position errors than csc

[bugzilla-daemon at bugzilla.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 jonpryor at vt.edu.

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

--- shadow/82444	2007-08-21 18:17:49.000000000 -0400
+++ shadow/82444.tmp.9360	2007-08-21 22:30:07.000000000 -0400
@@ -72,6 +72,19 @@
 
 ------- Additional Comments From remy.suen at gmail.com  2007-08-21 18:17 -------
 Hi, has there been any updates for this bug? I need to graphically
 mark C# files based on the compiler's output and this discrepancy
 makes the underlining different (or rather, plain out wrong,) if the
 user is using tabs instead of spaces.
+
+------- Additional Comments From jonpryor at vt.edu  2007-08-21 22:30 -------
+Many (most) Unix programs assume that tab == 8 spaces, in particular
+cat(1), or default to tab being 8 spaces (gedit, vim, emacs...).
+
+In order for error messges to be correct, the appropriate platform
+assumptions (tab == 8 spaces) must be followed.  (See also gcc, Perl,
+Python, and every other compiler/interpreter ever written on Unix.)  I
+don't see CSC.EXE-compatible numbering happening anytime soon.
+
+The best you could likely hope for is an additional mcs option to set
+the number of spaces a tab is equal to, or an environment variable. 
+I'm not sure how much support there would be for this, though.