|
virtual void | bit_array_cbk (GdsRecords::EnumType record_type, GdsData::EnumType data_type, vector< int > const &vBitArray)=0 |
| bit array callback More...
|
|
virtual void | integer_2_cbk (GdsRecords::EnumType record_type, GdsData::EnumType data_type, vector< int > const &vInteger)=0 |
| 2-byte integer callback More...
|
|
virtual void | integer_4_cbk (GdsRecords::EnumType record_type, GdsData::EnumType data_type, vector< int > const &vInteger)=0 |
| 4-byte integer callback More...
|
|
virtual void | real_4_cbk (GdsRecords::EnumType record_type, GdsData::EnumType data_type, vector< double > const &vFloat)=0 |
| 4-byte floating point number callback More...
|
|
virtual void | real_8_cbk (GdsRecords::EnumType record_type, GdsData::EnumType data_type, vector< double > const &vFloat)=0 |
| 8-byte floating point number callback More...
|
|
virtual void | string_cbk (GdsRecords::EnumType record_type, GdsData::EnumType data_type, string const &str)=0 |
| string callback More...
|
|
virtual void | begin_end_cbk (GdsRecords::EnumType record_type)=0 |
| begin or end indicator of a block More...
|
|
Kernel callbacks for GdsReader. These callbacks use enum for record_type and data_type, which is faster than ascii callbacks.
============================================================= Why do I need to wrap GdsDataBaseKernel into GdsDataBase? This is mainly for backward compatibility reasons. In old version limbo library, user only needs to implement child database class for GdsDataBase and use those ascii callbacks. I hope user does not need to change their code in the new version, so the old api must still be available. By adding new base class GdsDataBaseKernel, it is possible to achieve both. If user want to use old api, they can write child class for GdsDataBase,
while if they want to use new api, please inheritate GdsDataBaseKernel.
Definition at line 39 of file GdsReader.h.