#include <result.h>
Inheritance diagram for pqxx::Result::const_iterator:
Public Member Functions | |
pointer | operator-> () const |
reference | operator * () const |
const_iterator | operator++ (int) |
const_iterator & | operator++ () |
const_iterator | operator-- (int) |
const_iterator & | operator-- () |
const_iterator & | operator+= (difference_type i) |
const_iterator & | operator-= (difference_type i) |
bool | operator== (const const_iterator &i) const |
bool | operator!= (const const_iterator &i) const |
bool | operator< (const const_iterator &i) const |
bool | operator<= (const const_iterator &i) const |
bool | operator> (const const_iterator &i) const |
bool | operator>= (const const_iterator &i) const |
const_iterator | operator+ (difference_type o) const |
const_iterator | operator- (difference_type o) const |
difference_type | operator- (const_iterator i) const |
Result::size_type | num () const |
Friends | |
class | Result |
const_iterator | operator+ (difference_type o, const_iterator i) |
A Result, once obtained, cannot be modified. Therefore there is no plain iterator type for Result. However its const_iterator type can be used to inspect its Tuples without changing them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The iterator "points to" its own Tuple, which is also itself. This allows a Result to be addressed as a two-dimensional container without going through the intermediate step of dereferencing the iterator. I hope this works out to be similar to C pointer/array semantics in useful cases[2]. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|