Class Hierarchy
This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 12345]
Crili::service::SocketBase::Acceptor | Abstract interface for incomming TCP/IP connections acceptor (used in servers ) |
▼Crili::stream::view::Base | Interface for stream already avaliable data view |
Crili::stream::view::Default | Provide basic view implementation |
▼Crili::Color | Base for all color models |
Crili::color::ANSI16 | The ANSI16 class |
Crili::color::ANSI256 | The ANSI256 class |
Crili::color::CMYK | The CMYK class |
Crili::color::CSS | The CSS class |
Crili::color::GRAY | The GRAY class |
Crili::color::HCG | The HCG class |
Crili::color::HSL | The HSL class |
Crili::color::HSV | The HSV class |
Crili::color::HWB | The HWB class |
Crili::color::LAB | The LAB class |
Crili::color::LCH | The LCH class |
Crili::color::RGB | The RGB class |
Crili::color::XYZ | The XYZ class |
▼Crili::service::ComputeBase | The rili::service::ComputeBase class provide interface to schedule asynchronous long runing task in another thread to not block current |
Crili::service::Compute | Default ComputeBase service implementation |
Crili::Context | Used as scheduler for tasks execution on single thread |
Crili::XML::DocumentType | Used to store document - it do not have own markup - it's just root element for all other elements in XML document |
▼Cstd::exception | STL class |
Crili::JSON::SyntaxError | Used to communicate about invalid JSON synthax |
▼Crili::service::SocketBase::CreateAcceptorError | |
Crili::service::SocketBase::CreateAcceptorBindError | Error type which should be used in case when during creating Acceptor is problem with socket association after correctly resolved dns address |
Crili::service::SocketBase::CreateAcceptorResolveError | Error type which should be used in case when dns resolver cannot resolve address during creating Acceptor |
▼Crili::service::SocketBase::CreateConnectionError | |
Crili::service::SocketBase::CreateConnectionConnectError | Error type which should be used in case when during creating Connection is problem with socket association after correctly resolved dns address |
Crili::service::SocketBase::CreateConnectionResolveError | Error type which should be used in case when dns resolver cannot resolve address during creating Connection |
▼Crili::stream::error::Error | Base stream error |
▼Crili::stream::error::EndOfData | Base stream error indicating end of data(writable or readable) |
▼Crili::stream::error::ReadableEnd | Stream error indication end of readable steam |
Crili::service::SocketBase::Connection::ReadableWouldBlock | Error type which should be used in non-blocking connection mode when read operation fail, but if connection was in blocking mode read oparation would block instead |
▼Crili::stream::error::WritableEnd | Stream error indication end of writable steam |
Crili::service::SocketBase::Connection::WritableWouldBlock | Error type which should be used in non-blocking connection mode when write operation fail, but if connection was in blocking mode write oparation would block instead |
Crili::stream::error::OutOfRange | Steam errorr indicating value reading error because of too small range of provided variable |
Crili::stream::error::UnexpectedData | Stream error indicating unexpected data in stream |
Crili::XML::SyntaxError | Used to communicate about invalid XML synthax |
▼Cstd::runtime_error | STL class |
Crili::ComplexException | Used to store more than one exceptions which caused final error occurance. Useful to trace reason of complex operation failure |
Crili::promise::PromiseCanceled | Exception which will be used as error for rejection through rili::CancelablePromise::cancel or rili::CancelablePromise<void>::cancel |
▼Crili::test::Formater | Interface which can be used to indicate about exents, which occure during tests exacution |
Crili::test::BasicFormater | Default formater, which log test results similarly like gtest |
▼Citerator | |
Crili::stream::ReadableCustomIterator< T > | The ReadableCustomIterator class give similar functionality like std::istream_iterator but work with rili Readable streams instead std::istream and utilize custom Reader for given type |
Crili::stream::ReadableIterator< T > | The ReadableIterator class give similar functionality like std::istream_iterator but work with rili Readable streams instead std::istream and utilize default Readable stream serializer for given type |
Crili::stream::WritableCustomIterator< T > | The WritableCustomIterator class give similar functionality like std::ostream_iterator but work with rili Writable streams instead std::ostream and utilize custom Writer for given type |
Crili::stream::WritableIterator< T > | The WritableIterator class give similar functionality like std::ostream_iterator but work with rili Writable streams instead std::ostream and utilize default Writable stream serializer for given type |
Crili::JSON | The Value class is abstraction over JSON tree node |
Crili::service::SocketBase::Connection::ModeGuard | The ModeGuard is RAII style class which set given Mode on given Connection in it's lifetime scope |
Crili::stream::OperationResult | Used to indicate status of stream operation |
▼CPromiseBase | |
▼Crili::Promise< PromisedType > | The rili::Promise class provide unified API for asynchronous operations, which follow in most cases A+ Promises requirements |
Crili::CancelablePromise< PromisedType > | The rili::CancelablePromise class provide unified API for asynchronous operations, which follow in most cases A+ Promises requirements |
▼Crili::Promise< void > | The rili::Promise class provide unified API for asynchronous operations, which follow in most cases A+ Promises requirements |
Crili::CancelablePromise< void > | The rili::CancelablePromise class provide unified API for asynchronous operations, which follow in most cases A+ Promises requirements |
▼Crili::stream::Readable | Represent abstraction for readable stream sequence |
▼Crili::stream::BufferingReadable | Interface specialization of Readable which use buffer view (view::Default) |
Crili::stream::std::Readable | Wrapper which use std::istream as source of unformated data |
▼Crili::stream::Duplex | Represent abstraction for both readable and writable stream |
▼Crili::service::ConsoleBase | Interface for all Console service implementations |
Crili::service::Console | Simple implementation of Console service |
Crili::service::SocketBase::Connection | Stream oriented abstract base interface for duplex TCP/IP connection implementations |
Crili::stream::BufferingFifoDuplex | Specialization of Duplex which use single buffer both for read and write operations. Data is inserted at the end of buffer and retrieved from beginning of buffer |
▼Crili::stream::ReadableFileProxy | Use open writable FILE* to read data but not manage it lifetime |
Crili::stream::ReadableFile | RAII stream which is able to read data sequentially from file |
▼Crili::service::SocketBase | Abstract interface for service implementations which provide simple TCP/IP networking API |
Crili::service::Socket | Default, singleton implementation of SocketBase |
Crili::StateMachine< StateBaseType, StorageType > | The StateMachine class is basic implementation of object oriented, polimorphic Finite State Machine. It is quiet similar to State design pattern |
▼Cstreambuf | |
Crili::stream::std::ReadableStreambuf | Wrapper of std::streambuf which as unformted data source use Readable |
Crili::stream::std::WritableStreambuf | Wrapper of std::streambuf which as unformted data sink use Writable |
▼Cstd::system_error | STL class |
Crili::service::SocketBase::Acceptor::Error | Used when acceptor have internal failure |
Crili::TaskGuard | Used as RAII wrapper around rili::Context::reserve() and rili::Context::release() methods |
Crili::test::TestBaseFixture | Base class for test fixture used directly by TEST macro and indirect by TEST_F because TestBaseFixture must be base class for use provided fixture |
Crili::test::TestStorage | The TestStorage is used to store registered tests |
▼Crili::service::TimeBase | Interface class for Time service which give ability to create promises which will be resolved after some time |
Crili::service::Time | Default TimeBase service implementation |
Crili::XML::TreeType | Used to store tree type nodes |
Crili::TypeId | Can be used as very lightweight replacement for RTTI |
Crili::Variant< Types > | Variant is data structure which can be used like union but allow to store non-POD types |
Crili::Variant< bool, std::string, ArrayType, ObjectType > | |
Crili::Variant< TextType, CDATAType, CommentType, DoctypeType, DeclarationType, rili::XML::TreeType, rili::XML::DocumentType > | |
▼Crili::Variant< Types... > | |
Crili::SiblingVariant< Base, Types > | SiblingVariant is data structure which can be used like union of given Base type derived types |
▼Crili::stream::Writable | Represent abstraction for writable stream sequence |
▼Crili::stream::BufferingWritable | Interface specialization of Writable which use buffer view (view::Default) |
Crili::stream::std::Writable | Wrapper which use std::ostream as sink for unformated data |
Crili::stream::Duplex | Represent abstraction for both readable and writable stream |
▼Crili::stream::WritableFileProxy | Use open writable FILE* to flush data but not manage it lifetime |
Crili::stream::WritableFile | Create stream which can be used to write data to given file |
Crili::XML | Represent generic XML node |