Skip to main content

Publications by C++ experts

Articles by experts are saught after the most. Therefore, here are the links to the articles written by some of my favorite authors (in no particular order).

Comments

Anonymous said…
Robert Martin link appears broken
Mon Feb 05, 06:02:00 AM PST
Comptrol said…
Hi brother, greeetings from Turkey.

I think you should add stanley lippman in that list as well-although he hasn't written for a long time.

his articles:

http://msdn.microsoft.com/en-us/magazine/cc159481.aspx

and his blog, consisting of his old articles:

http://blogs.msdn.com/slippman/

keep up the good work, you are one of the few people encouraging me to put up with c++ :P
Sun May 04, 03:17:00 AM PDT
Sumant said…
Hi,
Thanks for your encouragement! Adding Stan Lippman in the list makes perfect sense. I'm wondering why his name did not pop up in my head.

One very good reason to stay up-to-date with latest C++ is the upcoming C++09 standard (http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2008/n2565.html) which will take C++ to a whole new level of power and complexity!

- Sumant.
Sun May 04, 02:04:00 PM PDT
Anonymous said…
Hi,
Thanks for your encouragement! Adding Stan Lippman in the list makes perfect sense. I'm wondering why his name did not pop up in my head.
gclub
Sat Jun 24, 10:01:00 AM PDT
Post a Comment

Popular Content

Unit Testing C++ Templates and Mock Injection Using Traits

Unit testing your template code comes up from time to time. (You test your templates, right?) Some templates are easy to test. No others. Sometimes it's not clear how to about injecting mock code into the template code that's under test. I've seen several reasons why code injection becomes challenging. Here I've outlined some examples below with roughly increasing code injection difficulty. Template accepts a type argument and an object of the same type by reference in constructor Template accepts a type argument. Makes a copy of the constructor argument or simply does not take one Template accepts a type argument and instantiates multiple interrelated templates without virtual functions Lets start with the easy ones. Template accepts a type argument and an object of the same type by reference in constructor This one appears straight-forward because the unit test simply instantiates the template under test with a mock type. Some assertion might be tested in...
Post a Comment
Read more

Covariance and Contravariance in C++ Standard Library

Covariance and Contravariance are concepts that come up often as you go deeper into generic programming. While designing a language that supports parametric polymorphism (e.g., templates in C++, generics in Java, C#), the language designer has a choice between Invariance, Covariance, and Contravariance when dealing with generic types. C++'s choice is "invariance". Let's look at an example. struct Vehicle {}; struct Car : Vehicle {}; std::vector<Vehicle *> vehicles; std::vector<Car *> cars; vehicles = cars; // Does not compile The above program does not compile because C++ templates are invariant. Of course, each time a C++ template is instantiated, the compiler creates a brand new type that uniquely represents that instantiation. Any other type to the same template creates another unique type that has nothing to do with the earlier one. Any two unrelated user-defined types in C++ can't be assigned to each-other by default. You have to provide a...
14 comments
Read more

Multi-dimensional arrays in C++11

What new can be said about multi-dimensional arrays in C++? As it turns out, quite a bit! With the advent of C++11, we get new standard library class std::array. We also get new language features, such as template aliases and variadic templates. So I'll talk about interesting ways in which they come together. It all started with a simple question of how to define a multi-dimensional std::array. It is a great example of deceptively simple things. Are the following the two arrays identical except that one is native and the other one is std::array? int native[3][4]; std::array<std::array<int, 3>, 4> arr; No! They are not. In fact, arr is more like an int[4][3]. Note the difference in the array subscripts. The native array is an array of 3 elements where every element is itself an array of 4 integers. 3 rows and 4 columns. If you want a std::array with the same layout, what you really need is: std::array<std::array<int, 4>, 3> arr; That's quite annoying for...
20 comments
Read more