The good news about Erlang can be summed up at this: Erlang is the culmination of twenty-five years of correct design decisions in the language and platform. Whenever I've wondered about how something in Erlang works, I have never been disappointed in the answer. I almost always leave with the impression that the designers did the “right thing”. I suppose this is in contrast to Java, which does the pedantic thing, Perl, which does the kludgy thing, Ruby, which has two independent implementations of the wrong thing, and C, which doesn't do anything.
This post is part of a series - go here for the index. Welcome back! The previous post gave us a lot of theoretical groundwork on triangles. This time, let's turn it into a working triangle rasterizer. Again, no profiling or optimization this time, but there will be code, and it should get us set…
O. Callaú, R. Robbes, \. Tanter, and D. Röthlisberger. Proceedings of the 8th Working Conference on Mining Software Repositories, page 23--32. New York, NY, USA, ACM, (2011)
G. Schreiber, A. Stemmer, and R. Bischoff. IEEE Workshop on Innovative Robot Control Architectures for Demanding (Research) Applications How to Modify and Enhance Commercial Controllers (ICRA 2010), page 15--21. Citeseer, (2010)