On 2008 Aug 17, at 23:45, Paul Jarc wrote:
A somewhat related issue: I'd like to avoid hard-coding the path to
runhaskell or ghc in the #! line. Instead, I'd like to use #!/bin/sh,
and have the shell find runhaskell or ghc in $PATH. This means the
#! /usr/bin/env runhaskell ...
--
brandon
Bertram Felgenhauer <[EMAIL PROTECTED]> wrote:
> Paul Jarc wrote:
>> Maybe runhaskell should automatically add "-x hs" to the ghc
>> command?
>
> The 6.9 branch version of runghc does that, actually.
Ah, that's good news.
> There's an undocumented runghc flag which I found by looking at the
> sou
On 18/08/2008, at 8:13 PM, Simon Marlow wrote:
So would I usually, though I've had to turn down cc flags to get
darcs
to build on ia64 before (SHA1.hs generates enormous register
pressure).
We should really use a C implementation of SHA1, the Haskell version
isn't buying us anything beyon
Duncan Coutts wrote:
On Fri, 2008-08-15 at 15:12 +0100, Ian Lynagh wrote:
On Fri, Aug 15, 2008 at 11:12:20AM +1000, Manuel M T Chakravarty wrote:
Moreover, as I wrote a few times before, some reasons for switching in
the first place are invalidated by not having the core libraries in
git, to
Manuel M T Chakravarty wrote:
From what you are saying, it seems that one "advantage" of git
(in-place branch switching) is not going to be useful to GHC in any case
(because we use nested repositories).
As far as I can tell, in-place branches are not a lot of use to us compared
to just havi
On Mon, Aug 18, 2008 at 12:28:03PM +1000, Manuel M T Chakravarty wrote:
>
> does using merge mean that we need to use in-place branch switching
No; when you "git pull" (the equivalent of darcs pull -a) it will pull
and merge the changes (unless you ask it to rebase them instead of
merging them).
On Mon, Aug 18, 2008 at 12:21:47PM +1000, Manuel M T Chakravarty wrote:
> From what you are saying, it seems that one "advantage" of git (in-
> place branch switching) is not going to be useful to GHC in any case
Yes.
> (because we use nested repositories).
That does make it harder, but the m
Paul Jarc wrote:
> I have a Haskell script called "notify", without a .hs extension,
> which causes some problems. (I'm using ghc 6.8.3.)
>
> First attempt: runhaskell notify
> Without the .hs extension, ghc doesn't know it's a Haskell script, and
> so I get "Could not find module `notify'". May
Meanwhile Ian has updated the download page.
Although it was built on a G5 with Tiger it should also run on a G4 with
Leopard. (and was reported to run on G4 with Tiger)
Christian
Benjamin L.Russell wrote:
On Tue, 05 Aug 2008 09:11:25 +0200, Christian Maeder
<[EMAIL PROTECTED]> wrote:
I've
