[Mono-bugs] [Bug 76577][Wis] New - TextWriter Mono/.NET behaviour variance

[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 bill.seddon at lyquidity.com.

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

--- shadow/76577	2005-10-27 18:47:42.000000000 -0400
+++ shadow/76577.tmp.11412	2005-10-27 18:47:42.000000000 -0400
@@ -0,0 +1,37 @@
+Bug#: 76577
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: bill.seddon at lyquidity.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: TextWriter Mono/.NET behaviour variance
+
+The implementation of the abstract TextWriter class results in behaviour 
+that is not the same between Mono and .NET.
+
+The Mono implementation of the WriteLine() methods call Write() methods.  
+In many cases this is OK but this implementation makes an assumption that 
+WriteLine is always super-set of Write().  However, the implementation of 
+the Write() and the WriteLine() methods may need to be different because 
+the concrete TextWriter implementation targets an output device where 
+this is necessary.  
+
+In this scenario, unless the concrete implementation overrides all the 
+virtual WriteLine() methods, the Write() method of the concrete 
+implementation is called instread of the required WriteLine() method.
+
+This behaviour is not the same as .NET.  .NET will use the WriteLine() 
+implementation of the concrete class when a caller executes a WriteLine() 
+under all circumstances.
+
+The change to the TextWriter implementation may not be significant.