So it sounds like what you need at the moment is more of a Haskell
pretty printer than a debugger. :)
IDEs, like Visual Studio, can be very helpful when writing code in a
language you don't really know, I've noticed this writing VBA. I
wish Visual Haskell were ready for real use.
-- Lennart
On Sep 6, 2006, at 08:13 , Tamas K Papp wrote:
On Wed, Sep 06, 2006 at 06:33:32AM -0400, Lennart Augustsson wrote:
I've also used Visual Studio, and I wouldn't mind having something
like that for Haskell. But I have to agree with Jon, I think the
best way of debugging is to understand your code. I think people who
come from imperative programming come with a mind set that you
understand your code by stepping through it in the debugger. But I
find this paradigm much less useful for functional code.
At this point, I need debugging not because I don't understand my
code, but because I don't understand Haskell ;-) Most of the mistakes
I make are related to indentation, precedence (need to remember that
function application binds tightly). The compiler and the type system
catches some mistakes, but a few remain.
Thanks for the suggestions.
Tamas
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
