#include <object_parser.hpp>
- Todo:
- revise class hierarchy (does it make sense to let the base of the parser object hierarchy to perform actual work, or should there be an abstract interface class on top of it?
◆ ObjectParser()
visr::objectmodel::ObjectParser::ObjectParser |
( |
| ) |
|
|
default |
◆ ~ObjectParser()
visr::objectmodel::ObjectParser::~ObjectParser |
( |
| ) |
|
|
virtualdefault |
Destructor (virtual). Virtual destructor is required since this objects are used polymorphically.
◆ parse()
void visr::objectmodel::ObjectParser::parse |
( |
boost::property_tree::ptree const & |
tree, |
|
|
Object & |
obj |
|
) |
| const |
|
pure virtual |
◆ write()
void visr::objectmodel::ObjectParser::write |
( |
Object const & |
obj, |
|
|
boost::property_tree::ptree & |
tree |
|
) |
| const |
|
pure virtual |
The documentation for this class was generated from the following files:
- C:/Local/dev/gitlab-runner/builds/a913a013/0/s3a/VISR/src/libobjectmodel/object_parser.hpp
- C:/Local/dev/gitlab-runner/builds/a913a013/0/s3a/VISR/src/libobjectmodel/object_parser.cpp