Well, I’ve now had 4 hours of time to work. My Saturday is getting broken up more than I anticipated and it looks like I’ll only get about 5 hours total today. We’ll see.
Well, I’ve now had 4 hours of time to work. My Saturday is getting broken up more than I anticipated and it looks like I’ll only get about 5 hours total today. We’ll see.
I’m getting ready to start a 7 hour challenge from my cousin to write a Elite style game called Ex Astris today.
Standard Algorithms Few C++ developers seem to appreciate that the standard C++ library is actually designed around functional programming principles.
I had noticed some references lately from Stroustrup (the inventor of c++) about not liking camel casing. He prefers underscores between words in variable names: myFunctionName vs my_function_name. The best reference I can find to this is from Stroustrup’s C++ FAQ page.
I friend of mine recently asked me what I thought of Lua. It is, after all, the first language that I chose to integrate with the rewrite of the Crate Game Engine. The language itself, the syntax and structure, I am somewhat indifferent about. However, I am interested in it for other reasons:
Due to a series of server mishaps that I will not bother going into right now, this website is now operating on a new server at a new host.
We’ve covered the “Assembly Language”, “C” and “C++” of the C++ threading world, and now we are going to try and move beyond that.
I’m going to cover a thread safety strategy I have been thinking about lately. Let’s look at an example for a typical “lock the variables as you use them” approach:
In my last posting about C++ Multiple Dispatch I wondered if it was really any different than function overloading. I now appreciate that it is something that needs to occur at runtime, not compile time.
I clearly must be missing something. I just noticed this article on the O’Reilly ONLamp blog, discussing multiple dispatch in Perl. The example code given:
