[Mono-bugs] [Bug 52709][Nor] Changed - System.Diagnostics.Debug methods unexpected behaviour when DEBUG defined

[bugzilla-daemon@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 t7@pobox.com.

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

--- shadow/52709	2004-01-09 13:38:16.000000000 -0500
+++ shadow/52709.tmp.13156	2004-01-09 14:02:49.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 52709
 Product: Mono/Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: Other
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: System
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: t7@pobox.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -70,6 +70,25 @@
   public static void Main(string[] args)
   {
     Debug.WriteLine("Hello developer!");
     Debug.Assert(false);
   }
 }
+
+------- Additional Comments From t7@pobox.com  2004-01-09 14:02 -------
+I just took a look at the source.  The methods look like this:
+
+                [Conditional("DEBUG")]
+                public static void Write (string message)
+                {
+                        TraceImpl.Write (message);
+                }
+                                                                     
+                                                                     
+                                                                     
+                          
+Looks to me (unsure) that DEBUG needs to be defined when the runtime
+is built for them to output anything.
+Is that the entended behaviour? i.e. that the System.Diagnostic
+classes are for diagnosing the runtime during its development rather
+than for the use of application developers?
+