LSSTApplications
10.0+286,10.0+36,10.0+46,10.0-2-g4f67435,10.1+152,10.1+37,11.0,11.0+1,11.0-1-g47edd16,11.0-1-g60db491,11.0-1-g7418c06,11.0-2-g04d2804,11.0-2-g68503cd,11.0-2-g818369d,11.0-2-gb8b8ce7
LSSTDataManagementBasePackage
|
Specialization for Flag fields. More...
#include <Flag.h>
Public Types | |
typedef bool | Value |
the type returned by BaseRecord::get More... | |
typedef boost::int64_t | Element |
the actual storage type (shared by multiple flag fields) More... | |
Public Member Functions | |
int | getElementCount () const |
Return the number of subfield elements (always one for scalars). More... | |
FieldBase () | |
FieldBase (int) | |
Static Public Member Functions | |
static std::string | getTypeString () |
Return a string description of the field type. More... | |
Protected Member Functions | |
void | stream (std::ostream &os) const |
Defines how fields are printed. More... | |
Specialization for Flag fields.
Flag fields are handled specially in many places, because their keys have both an offset into an integer element and the bit in that element; while other fields have one or more elements per field, Flags have multiple fields per element. This means we can't put all the custom code for Flag in FieldBase, and because Flags have an explicit Key specialization, we put the record access implementation in Key.
typedef boost::int64_t lsst::afw::table::FieldBase< Flag >::Element |
typedef bool lsst::afw::table::FieldBase< Flag >::Value |
|
inline |
|
inline |
|
inline |
|
inlinestatic |
|
inlineprotected |