g_sauthoff:
> Hi,
>
> I try to debug some existing Haskell-Code. Out of the blue I get a
> 'progname: Prelude.read: no parse'
> error message from GHC.
>
> Great.
>
> Well, the code includes
>
> # grep '\' *| wc -l
> 23 (sic!)
>
> calls to the read fn.
>
> Well, how do I compile a Haskell pro
Hello,
You can also just use reads which returns a list of (partial) parses.
-Jeff
[EMAIL PROTECTED] wrote on 12/19/2007 03:17:39 PM:
> Hi
>
> > > Well, how do I compile a Haskell program in such a way, that I
> > > get a useful error message from read? I mean, like the
> > > filename/linen
Hi
> > Well, how do I compile a Haskell program in such a way, that I
> > get a useful error message from read? I mean, like the
> > filename/linenumber of the calling expression for starters.
I use the Safe library to do this sort of stuff:
http://www-users.cs.york.ac.uk/~ndm/safe/
You can cal
Georg Sauthoff <[EMAIL PROTECTED]> writes:
> Well, how do I compile a Haskell program in such a way, that I
> get a useful error message from read? I mean, like the
> filename/linenumber of the calling expression for starters.
It's dirty, it's mean, but you can use CPP. (On one line, and with
gh
On Dec 19, 2007, at 11:53 , Georg Sauthoff wrote:
I try to debug some existing Haskell-Code. Out of the blue I get a
'progname: Prelude.read: no parse'
error message from GHC.
If you can install GHC 6.8.x, you can use ghci's interactive
debugger. See http://cgi.cse.unsw.edu.au/~dons/blog/2
Hi,
I try to debug some existing Haskell-Code. Out of the blue I get a
'progname: Prelude.read: no parse'
error message from GHC.
Great.
Well, the code includes
# grep '\' *| wc -l
23 (sic!)
calls to the read fn.
Well, how do I compile a Haskell program in such a way, that I
get a useful erro
