From: Mads L. <mad...@ya...> - 2008-05-26 19:04:59
|
Hi, shelarcy wrote: > Hi, > I'm sorry about my reply is late. > > On Thu, 15 May 2008 17:15:54 +0900, Eric Y. Kow <eri...@gm...> wrote: > > Shelarcy: any ideas? > > I found Mad's previous patch left an problem for Windows platform. > > http://article.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/423 > > Windows' stdout, stdin and stdout requires console. But we can build > wxHaskell GUI program without console by -optl-mwindows option. So, > withCharResult's "hPutStrLn stderr" causes problem. I fixed this problem > by using Debug.Trace.putTraceMsg instedad of hPutStrLn stderr. Have you actually observed that this is problem in the specific case with processExecAsyncTimed? I am asking because if you have observed it at windows, then what I thought was a Linux-only issue is also a Windows issue. After all, the putStrLn only happens in case of an error (negative unicode). Just to be clear, I am not arguing against the patch, I just want to know if the processExecAsyncTimed problem also occurs on windows. Greetings, Mads |