One part of doing C++ the right way is using automatic variables for everything you possibly can. However at some point in your C++ endeavours, you’re likely to be using a C API of some sort, with explicit method calls to manage lifecycles, which can make this more difficult. My work at Canonical has involved talking to lots of these sorts of APIs, many of them based on GNOME’s Glib. To make life easier, I have created a set of easy to use wrappers to manage the lifecycle Glib and GObject objects.
Over the last few years I have become a much bigger fan of dynamic languages like Ruby and Python. Today I was thinking about one of my old gripes about dynamic languages, which was a lack of method overloading.
I guess this is really just a link to someone’s Github project. It’s a spec-style testing framework for BASH that has helped me write tested shell scripts!
If you’re currently executing your target platform that you build your product from instead of a properly installed Eclipse, you will have troubles when you upgrade. Eclipse 3.5 and above don’t count plug-ins as installed by simply unzipping - the configuration meta data must refer to them. The best way is to download a complete Eclipse and unzip this somewhere on your build server, instead of assembling it from components at build time. Guess we should have been doing this all along.