EmptyCrate Software. Travel. Stuff.

Chapter 5 of Real World Haskell covers the creation of our first Haskell module. The chapter seems to come prematurely from my perspective. I am not yet concerned about making a module while I'm still trying to understand the language.

Chapter 4 of Real World Haskell begins with some details about functions with side effects and interacting with the outside world.

Chapter 3 of Real World Haskell is "Defining Types, Streamlining Functions."

At first glance Haskell seems to get stuck in it's own terseness, creating datastructures with no real structure, if you will.

Haskell example:
 

Chapter 1 of Real World Haskell covers the most basic aspects of the language, such as common operators and operator precedence and gives some overviews of aspects of the language.

The book Real World Haskell is receiving some amazing reviews on Amazon, with comments like

This by far is one of the best programming books not only on Haskell as the language, but also the fundamentals of pure functional programming in general. This book in my opinion is a game changer to bring Haskell to the forefront of people's attentions. Whether you've been a programmer for years or just starting out, this book fits both needs quite nicely. If only other books could live up to this standard.

The content of the book is available for free online as well.

Because of the excellent reviews and a desire to learn some more about functional programming I've decided to go through the book and will be doing some blogging about it.

In case you find yourself asking where I get the stuff from that I blog about and wondering if I'm just making stuff up; many of the "Nobody Understands C++" articles on this website are inspired by principles found in the book "C++ Coding Standards" by Herb Sutter and Andrei Alexandrescu. The book is a collection of items from previous books that the pair has worked on together. As such, if you do not own any of the previous books this one makes a great addition to your library.

The book covers 101 best practices guidelines for your C++ code. It does not cover things like indentation level and style of comments, the things that we have all come to consider to be part and parcel with a standards document. In fact, it explicitly avoids talking about those things and says that they should be internally consistent within each file. "C++ Coding Standards" covers topics on program design, object lifetime management, namespaces, generic programming (templates) and the standard library.