[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 19:17:13 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.

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

--- shadow/81159	2007-04-18 19:12:10.000000000 -0400
+++ shadow/81159.tmp.1085	2007-04-18 19:17:13.000000000 -0400
@@ -172,6 +172,24 @@
 now makes the 2.0 profile behave exactly like mscorlib 2.0's
 
 ------- Additional Comments From fejj at novell.com  2007-04-18 19:12 -------
 Created an attachment (id=19088)
 81159-2.patch
 
+
+------- Additional Comments From fejj at novell.com  2007-04-18 19:17 -------
+oh, btw, I tested out the eoln thing on Windows built against mscorlib
+and here's something interesting:
+
+say I type "abcdefghijklmno" and then hit Enter, the Read() result is:
+
+"abcdefghijklmno\r"
+
+if I then do another Console.In.Read() call, as you said, it again
+waits for me to hit Enter, so if I do just that, my second Read()
+results in:
+
+"\n\r\n"
+
+
+anyways, just thought it was interesting... might be useful to someone
+in the future :)


More information about the mono-bugs mailing list