Haskell's effect on my C++ : exploit the type system
vallettaventures.com
Haskell's effect on my C++ : exploit the type system
1–10 of 57 posts
Re: Haskell's effect on my C++ : exploit the type system
#2If your only example to show C++ verbosity fails to compile and is also patently wrong, you are not making a good point. (The constructor is private, the variable naming prevents short accessors such as Rectangle::width()). Better:
struct Rectangle { double x,y, width, length; };
int main() { Rectangle r = {0., 0., 10., 10. }; return 0; }
This even compiles in C++03. If you really insist on private members, you will need initializer lists and some changed member names.
The small example error has been worked around with for years by simply placing the constant on the left side of the comparison. Not pretty, but effective.
I agree with the general point, though. A functional style can make C++ much more efficient. It is also the only way to do template meta-programming and everybody who tries to go into that direction can benefit from learning Haskell.
Re: Haskell's effect on my C++ : exploit the type system
#3If your only example to show C++ verbosity fails to compile and is also patently wrong, you are not making a good point. (The constructor is private, the variable naming prevents short accessors such as Rectangle::width()). Better: struct Rectangle { double x,y, width, length; }; int main() { Rectangle r = {0., 0., 10., 10. }; return 0; } This even compiles in C++03. If you really insist on private members, you will…
Re: Haskell's effect on my C++ : exploit the type system
#4If your only example to show C++ verbosity fails to compile and is also patently wrong, you are not making a good point. (The constructor is private, the variable naming prevents short accessors such as Rectangle::width()). Better: struct Rectangle { double x,y, width, length; }; int main() { Rectangle r = {0., 0., 10., 10. }; return 0; } This even compiles in C++03. If you really insist on private members, you will…
bookmarked: http://bartoszmilewski.com/2011/07/11/monads-in-c/ http://bartoszmilewski.com/2010/11/29/understanding-c-concep...
I should have mentioned those articles. They are a great example of Haskell influencing a C++ programmer. Although this article might show what the average C++ programmer thinks `using the type system`, `verbosity` and `influencing their style` mean.
Re: Haskell's effect on my C++ : exploit the type system
#5 > Although the newcomer C# was only introduced ten years
> ago, there is little in the language to reflect the
> thirty years of research into programming languages since
> C++ was introduced.
Re: Haskell's effect on my C++ : exploit the type system
#6map and fold are available in C++, though they're called std::transform (in ) and std::accumulate (in ). Totally agree with the author's point, the C++ I write nowadays is heavily influenced by my Scala/Haskell/Lisp exposure and is much better for it.
Re: Haskell's effect on my C++ : exploit the type system
#7Do people really still make the `=` vs `==` mistake? GCC -Wall has had "warning: suggest parentheses around assignment used as truth value" since as long as I can remember.
Re: Haskell's effect on my C++ : exploit the type system
#8you don't pick the language. The language picks you!
Re: Haskell's effect on my C++ : exploit the type system
#9[deleted]
Re: Haskell's effect on my C++ : exploit the type system
#10> Although the newcomer C# was only introduced ten years > ago, there is little in the language to reflect the > thirty years of research into programming languages since > C++ was introduced. Not a huge fan of C#, but he couldn't have picked a worse example for language stagnation .
I can say form experience that C# has several interesting features built on research from Haskell, just gotta probe the edges a bit. And once you probe the edges too hard your code becomes worthless for the standard blub programmer who'd prefer not have to learn the syntax.