[Mono-bugs] [Bug 81729][Nor] Changed - Console.Read(Line) doesn't block for winexe's
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri May 25 11:51:16 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 rolfkvinge at ya.com.
http://bugzilla.ximian.com/show_bug.cgi?id=81729
--- shadow/81729 2007-05-25 08:47:32.000000000 -0400
+++ shadow/81729.tmp.25405 2007-05-25 11:51:16.000000000 -0400
@@ -62,6 +62,21 @@
The 2nd way is to solve this in managed code (using a NullStream
in Console.cs) with the drawback that p/invoked unmanaged libs
could still block the app while trying to read from stdin.
(IMHO, we should not introduce this limitation in unix at all).
+
+------- Additional Comments From rolfkvinge at ya.com 2007-05-25 11:51 -------
+There's winforms applications out there that for some weird reason
+uses Console.ReadLine while initializing. On Mono all that happens is
+that when I execute the program the console just sits there, and
+there's not really easy to figure out that all I have to do is hit
+enter for the application to appear.
+
+I think the best solution would be as you said would be to "fix"
+Console to not do anything for winexe applications (at least not
+block on anything). I can't really see how printing CWL's when
+there's not supposed to be any can do much harm, but blocking on
+CR(L) is worse... And if there's any unmanaged lib that uses stdin,
+then that's just bad luck. Shouldn't be that many for winforms
+applications anyways.
More information about the mono-bugs
mailing list