#include <Point3r.h>
Public Member Functions | |
| Point3r () | |
| Point3r (const Point3r &src) | |
| Point3r (real xx, real yy, real zz) | |
| Point3r (const real *data) | |
| void | set (real xx, real yy, real zz) |
| void | set (real *data) |
| real & | operator[] (unsigned int i) |
| const real & | operator[] (unsigned int i) const |
| void | operator+= (const Vec3r &v) |
| void | operator-= (const Vec3r &v) |
| void | operator *= (real scalar) |
| void | operator/= (real scalar) |
| bool | operator== (const Point3r &v) const |
| bool | operator!= (const Point3r &v) const |
Public Attributes | |
| real | x |
| real | y |
| real | z |
Definition at line 55 of file Point3r.h.
|
|
|
|
|
|
|
||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
Definition at line 141 of file Point3r.h. References opal::Vec3r::x, x, opal::Vec3r::y, y, opal::Vec3r::z, and z. |
|
|
Definition at line 148 of file Point3r.h. References opal::Vec3r::x, x, opal::Vec3r::y, y, opal::Vec3r::z, and z. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
Definition at line 95 of file Point3r.h. Referenced by opal::Rayr::Rayr(). |
|
|
X-coordinate.
Definition at line 59 of file Point3r.h. Referenced by opal::distance(), opal::operator *(), operator *=(), operator!=(), opal::operator+(), operator+=(), opal::operator-(), operator-=(), opal::operator/(), operator/=(), opal::operator<<(), operator==(), operator[](), Point3r(), and set(). |
|
|
Y-coordinate.
Definition at line 62 of file Point3r.h. Referenced by opal::distance(), opal::operator *(), operator *=(), operator!=(), opal::operator+(), operator+=(), opal::operator-(), operator-=(), opal::operator/(), operator/=(), opal::operator<<(), operator==(), operator[](), Point3r(), and set(). |
|
|
Z-coordinate.
Definition at line 65 of file Point3r.h. Referenced by opal::distance(), opal::operator *(), operator *=(), operator!=(), opal::operator+(), operator+=(), opal::operator-(), operator-=(), opal::operator/(), operator/=(), opal::operator<<(), operator==(), operator[](), Point3r(), and set(). |
1.4.6-NO