OpenZGY/C++ API and Internals (ALPHA)
Access seismic data stored in ZGY format.
Public Member Functions | Static Protected Member Functions | List of all members
InternalZGY::Config Class Referenceabstract

#include <file.h>

Inheritance diagram for InternalZGY::Config:
InternalZGY::FileConfig

Public Member Functions

virtual std::string dump () const =0
 

Static Protected Member Functions

static std::string _get_string_env (const std::string &value_from_cf, const std::string &cfname, const std::string &envname, const std::string &dflt)
 
static std::int64_t _get_numeric_env (std::int64_t value_from_cf, const std::string &cfname, const std::string &envname, std::int64_t dflt, std::int64_t min_value, std::int64_t max_value)
 
static std::string _redact (const std::string &)
 

Detailed Description

A concrete Config instance is specific to the back-end that uses it. It is normally populated from an IOContext and is not directly visible to application code. The jury is still out regarding whether class IOContext should be backend specific or just a stringly typed dictionary.

TODO-High: For now just remove Config completely and use the application visible IOContext. I can re-introduce {File,SD}Config later as a trivial mapping of the corresponding IOContext just to improve isolation.


The documentation for this class was generated from the following files: