site Search Results

Results for: Andrew Koenig

Declarations and Reliability

The previous discussion about auto left me with a nagging doubt, which I would like to discuss here. - C/C++

Why Moving An Object Does Not Destroy the Original

When I first learned about how C++ moves data, I thought there must have been a design mistake. - C/C++

Why It Is Useful to Move Objects

We continue last week's discussion by showing why it is useful to know that an object is about to be recycled. - C/C++

Two Kinds of References

This post provides some of the background behind one of C++'s odder rules, namely the one that requires a nonconst reference to be attached to an lvalue. - C/C++

C++0x's Tools for Library Authors



Four additions to the language greatly facilitate writing C++ libraries. - C/C++

Moving Data — Why It Matters

This post, and the next few, will go into more detail about the idea of moving (rather than copying) data, along with some of the surrounding history and theory. - C/C++

The Last Word on auto (For Now)

The discussion about auto has meandered about a bit, so I'd like to point out what I think are the important themes. - C/C++

More Uses for auto

This post continues last week's discussion of auto by showing some more contexts in which it makes programs easier to read. - C/C++

3 Most Useful Library Features of C++0x

Part 2 of our series on C++0x illustrates moving data without copying it, smart pointers, and lambda expressions - C/C++

The auto Controversy

Several readers have spoken out about auto. Rather than responding to those comments individually, I thought I'd explain my thinking in more detail. - C/C++

Previous 13 14 15 16 17 18 19 20 21 22 Next