Since Heron syntax is C++ based, I am experimenting to see what happens when you drop the requirement for the this keyword.

Test Driven Development (TDD) represents the state of the art of development processes, but what's next?

In languages like C++, functions return temporary stack allocated values which can be very inefficient. I am using a technique on Heron which I call transfer semantics to provide a work-around.

Here, I describe an interpreted subset of Heron called HeronScript and I talk a bit about my short and long term plans.

Heron is going to need a killer-app if it has any hope of surviving. I may have found one ... teaching programming.

Chuck Allison stated in his latest article the unfortunate fact: "C++ novices don't learn templates, let alone CRTP, in their first week". This represents one of the big problems with how C++ is taught to novices.

Automating the delegation of implementation of an interface to an expression.

A rather unpleasant name, but a very useful pattern.

C++ templates enable a powerful variant of the Adapter Pattern, which I call the Generic Adapter Pattern. I think it helps illustrate how OO design patterns go together well with generic programming techniques.

Inspired by Kevlin Henney's boost::any variant type I have written a high performance alternative called cdiggins::any.

Here is an interesting problem with making C++ style concepts a real type in a programming language.

This is a very simple statement, but I don't like what C++ does with it.

I am in the middle of implementing the Heron standard library, and I have found two techniques for implementing container concepts. One is more object-oriented and the other is more generic. Which should I use?

One of my pet peeves is when people reference Wikipedia as an authoritative source for computer science defintions.

I am conducting a survey to find out what it would take for a new programming language to impress people.