On Wed, 2005-02-16 at 09:18 +0200, Krasimir Angelov wrote:
Hi Duncan
With ghc-6.4 the output from Debug.Trace.trace will be redirected to
the debug console when the application is compiled with --subsystem
windows. You can see the trace messages with any Windows debuger. The
error messages
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout fail without raising an
exception when the application is compiled with --subsystem
windows?
I think the current behaviour is the right one. After all we don't
have valid
On Wed, 2005-02-16 at 14:31 +0200, Krasimir Angelov wrote:
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout fail without raising an
exception when the application is compiled with --subsystem
windows?
I think the
On 16 February 2005 14:06, Duncan Coutts wrote:
On Wed, 2005-02-16 at 14:31 +0200, Krasimir Angelov wrote:
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout fail without
raising an exception when the application is
On Wed, 2005-02-16 at 14:49 +, Simon Marlow wrote:
On 16 February 2005 14:06, Duncan Coutts wrote:
On Wed, 2005-02-16 at 14:31 +0200, Krasimir Angelov wrote:
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout
This might be a bug report but it's definitely a question on what the
behaviour should be:
On windows if you link using --subsystem windows then your program
starts without popping up a console. This is good for GUI apps (and we
would like to make it the default when using gtk2hs on win32 by
Hi Duncan
With ghc-6.4 the output from Debug.Trace.trace will be redirected to
the debug console when the application is compiled with --subsystem
windows. You can see the trace messages with any Windows debuger. The
error messages from any uncaught exception will be displayed in
message box.
