29jul09
«
rules of thumb
patterns «
What do I put in the api of each C++ class? It often looks like I select parts from an à la carte menu of features. If you don't know gross patterns, each api can look complex. But if you replaced sections of boilerplate with a pattern name, each api would seem simple. Below I list typical code patterns I use.
Thus, below I present a compression scheme, to let you see a class as smaller since multi-line chunks can be swapped for a single pattern name. While I don't think of these as "design patterns," that idea might loosely apply.
stub «
So far this page is just a stub, but a brief intro above should give you the right idea about future direction of content I plan to put here.
