... strict typing is getting in the way....

When Haskell's strict typing seems to get in your way, chances are more that you are heading for a big and nasty problem (aka, bug) sometime down the line, unless you are extremely careful of what you do.

Strict typing is a boon to software designers in that it helps point out even major design flaws and that too rather earlier.

But, apart from this, if one is trying to deal with a computational problem involving lots and lot of state-change (and things like memoization etc), then there is no "easy" way out for a beginner in Haskell. IMHO, that's because, Haskell isn't modelled after the so called state-change model of computation.

But I am sure, Haskell Gurus out there may help you out if you give more inputs about your problem.

-Damodar

On Sun, Sep 9, 2012 at 1:45 PM, KC <kc1956@gmail.com> wrote:
If one programming language suited every computable problem there
would only be one programming language.

You don't seem to have a point worth making without more description
of your problem.


On Sun, Sep 9, 2012 at 1:10 AM, Dennis Raddle <dennis.raddle@gmail.com> wrote:
> Sadly, I've decided Haskell is not the right language for my current
> project. Python is better. I need to hack together data, and strict typing
> is getting in the way. Most of my algorithms are better served with
> imperative/mutable-data. I learned a lot about Haskell trying to do it, but
> my knowledge of the language is not quiet good enough and I feel like I'm
> fighting the language. Python is better. For now.
>
>
> _______________________________________________
> Beginners mailing list
> Beginners@haskell.org
> http://www.haskell.org/mailman/listinfo/beginners
>



--
--
Regards,
KC

_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://www.haskell.org/mailman/listinfo/beginners