RE: Re^2: Extra output lines from trace.

[Sigbjorn Finne (Intl Vendor)]

Hi,

changing the default back to what it was wouldn't
be a problem, but would it be the Right Thing? My
take on this is that you can easily enough define
versions of 'trace' *in Haskell* that decorate their
stderr output, if IOExts.trace doesn't do any.

module Utils ( trace ) where

import IOExts as Std ( trace )

trace :: String -> a -> a
trace msg = 
  Std.trace ("Trace On:\n" ++ msg ++ "\nTrace off.\n")

As it was, you had to resort to overriding some low-level
C hook RTS procedures to get non-decorative trace msgs,
which somehow feels wrong to me - using C as your
extension language.

Hmm..I guess religious wars have been started for less? :)

--sigbjorn

> Marc van Dongen [mailto:[EMAIL PROTECTED]] writes: 
> 
> Hi there,
> 
> This is related to at least two earlier
> messages in this forum which sadly enough I
> only noticed today.
> 
> It probably is a feature that since then
> trace doesn't print Trace on/Trace off anymore.
> 
> Is there any reason for not doing this
> anymore? In my opinion it makes tracing
> very awkward.
> 
> People who don't want Trace on/off could
> always redirect stderr to stdout and use a
> grep -v Trace.
> 
> Maybe adding a traceOnOff function?
> 
> 
> Regards,
> 
> 
> 
> Marc
>