Quantcast
Channel: When should I use pointers instead of references in API-design? - Stack Overflow
Viewing all articles
Browse latest Browse all 18

When should I use pointers instead of references in API-design?

$
0
0

I understand the syntax and general semantics of pointers versus references, but how should I decide when it is more-or-less appropriate to use references or pointers in an API?

Naturally some situations need one or the other (operator++ needs a reference argument), but in general I'm finding I prefer to use pointers (and const pointers) as the syntax is clear that the variables are being passed destructively.

E.g. in the following code:

void add_one(int& n) { n += 1; }void add_one(int* const n) { *n += 1; }int main() {  int a = 0;  add_one(a); // Not clear that a may be modified  add_one(&a); // 'a' is clearly being passed destructively}

With the pointer, it's always (more) obvious what's going on, so for APIs and the like where clarity is a big concern are pointers not more appropriate than references? Does that mean references should only be used when necessary (e.g. operator++)? Are there any performance concerns with one or the other?

EDIT (OUTDATED)

Besides allowing NULL values and dealing with raw arrays, it seems the choice comes down to personal preference. I've accepted the answer below that references Google's C++ Style Guide, as they present the view that "References can be confusing, as they have value syntax but pointer semantics.".

Due to the additional work required to sanitise pointer arguments that should not be NULL (e.g. add_one(0) will call the pointer version and break during runtime), it makes sense from a maintainability perspective to use references where an object MUST be present, though it is a shame to lose the syntactic clarity.


Viewing all articles
Browse latest Browse all 18

Latest Images

Trending Articles



Latest Images