cvs commit: fptools/ghc/includes Hooks.h fptools/ghc/rts RtsFlags.c fptools/ghc/rts/hooks RtsOpts.c

[Sigbjorn Finne]

Why is a crude global variable preferable to a routine which
(potentially) could insert lots of interesting computation
before returning the default set of options to use?

--sigbjorn

----- Original Message -----
From: "Simon Marlow" <simonmar@glass.cse.ogi.edu>
To: <cvs-ghc@haskell.org>
Sent: Monday, October 01, 2001 04:36
Subject: cvs commit: fptools/ghc/includes Hooks.h fptools/ghc/rts RtsFlags.c
fptools/ghc/rts/hooks RtsOpts.c


> simonmar    2001/10/01 04:36:29 PDT
>
>   Modified files:
>     ghc/includes         Hooks.h
>     ghc/rts              RtsFlags.c
>   Added files:
>     ghc/rts/hooks        RtsOpts.c
>   Log:
>   Allow default RTS options to be specified by linking in an object file
>   which defines the symbol `ghc_rts_opts' to point to a string of RTS
>   options.
>
>   This is preferred to using defaultsHook(), if possible.  Perhaps we
>   could remove defaultsHook().
>
>   (won't work with DLL's; if we ever ressurrect them we'll
>   have to deal with this somehow).
>
>   Revision  Changes    Path
>   1.6       +3 -1      fptools/ghc/includes/Hooks.h
>   1.51      +37 -21    fptools/ghc/rts/RtsFlags.c
>
> _______________________________________________
> Cvs-ghc mailing list
> Cvs-ghc@haskell.org
> http://www.haskell.org/mailman/listinfo/cvs-ghc