[Mono-bugs] [Bug 81159][Nor] Changed - Console.In.Read doesn't allow line-oriented input with mscorlib 2.0

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Apr 18 11:44:08 EDT 2007

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 fejj at novell.com.


--- shadow/81159	2007-04-18 09:07:07.000000000 -0400
+++ shadow/81159.tmp.21619	2007-04-18 11:44:08.000000000 -0400
@@ -43,6 +43,18 @@
 ------- Additional Comments From gert.driesen at pandora.be  2007-04-18 09:07 -------
 On 2.0 profile, the call to Console.In.Read finishes immediately 
 when 16 characters have been entered while on 1.0 (and MS 1.1 and 
 2.0) the call only returns after pressing enter.
+------- Additional Comments From fejj at novell.com  2007-04-18 11:44 -------
+hmmm, the behavior of waiting for Enter seems broken to me...
+curious. What happens if you hit Enter sometime before typing 16
+characters? Does it still read the first 16 characters? Or only up to
+the '\n'? And if it reads the full 16 characters, does it need to wait
+for another Enter?
+Also, what if I type, say, 20 characters before hitting Enter. What
+happens with those other 4 characters? are they dropped? or do they
+become the first 4 characters read by the next call to Console.In.Read()?

More information about the mono-bugs mailing list