[Mono-bugs] [Bug 46500][Nor] New - CSC namespace error that MCS doesn't catch

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Thu, 17 Jul 2003 01:35:16 -0400 (EDT)

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 peter@newton.cx.


--- shadow/46500	Thu Jul 17 01:35:15 2003
+++ shadow/46500.tmp.11316	Thu Jul 17 01:35:15 2003
@@ -0,0 +1,33 @@
+Bug#: 46500
+Product: Mono/MCS
+Version: unspecified
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: Misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: peter@newton.cx               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: CSC namespace error that MCS doesn't catch
+CSC seems to have implicit 'using' directives based on the namespace
+currently being compiled, or something like that. It will give compile
+errors on files that MCS accepts.
+Example:  Mono.Data.SybaseClient/Mono.Data.SybaseTypes/SybaseDecimal.cs
+MCS will compile Mono.Data.SybaseClient without complaints, but CSC will
+bomb with an error equivalent to "No such class Mono.Math.Pow, maybe you
+need a /r: flag."
+That file has "using System;" and invokes the function "Math.Pow", but for
+some reason CSC thinks it should look in the "Mono." namespace first (there
+is no "using Mono;" directive). The only reason I can think that it would
+do that would be because the namespace being compiled is
+Mono.Data.SybaseTypes. Clearly csc has no built-in Mono specifics.