Hi Chris,
> i have upgraded to doctest version 0.4.1.
> Now when i try to run the example from the webpage, i get:
>
> doctest: Interpreter exited with an error: ExitFailure 127
>
> What's wrong here and how can i fix it?
Can you still reproduce this on your system? If
On Wed, Sep 21, 2011 at 7:52 PM, informationen wrote:
> Do you have any idea, what the error message wants to tell
> me. What does "interpreter exited with .." mean. If i add a
Doctests starts ghc in interactive mode for evaluating the examples.
"interpreter exited with.." means that the spawned
On Wed, Sep 21, 2011 at 07:30:16PM +0300, Sakari Jokinen wrote:
On Tue, Sep 20, 2011 at 7:50 PM, informationen wrote:
doctest: Interpreter exited with an error: ExitFailure 127
You are trying the doctest binary from the command line and not the
library interface?
I tried this with ghc 7.0.3
On Tue, Sep 20, 2011 at 7:50 PM, informationen wrote:
> doctest: Interpreter exited with an error: ExitFailure 127
You are trying the doctest binary from the command line and not the
library interface?
I tried this with ghc 7.0.3 and doctest 0.4.1 but could not reproduce
it with "$
Hi,
i have upgraded to doctest version 0.4.1.
Now when i try to run the example from the webpage, i get:
doctest: Interpreter exited with an error: ExitFailure 127
What's wrong here and how can i fix it?
Kind regards
Chris
This is the content of Fib.hs:
module Fib where
-- | Co
hi.
I'm trying to run an system command (wget) within a CGI script and get the following
error:
>Exitfailure 127
How can I get more information out of an ExitFailure x error?
Can I use ioeGetErrorString? But this function doesn't work on ExitCode, which system
returns.
