uvw 3.1.0
|
Wrapper class for underlying types. More...
#include <uv_type.hpp>
Public Member Functions | |
virtual int | init () |
Initializes the handle. | |
loop & | parent () const noexcept |
Gets the loop from which the resource was originated. | |
const U * | raw () const noexcept |
Gets the underlying raw data structure. | |
U * | raw () noexcept |
Gets the underlying raw data structure. | |
Wrapper class for underlying types.
It acts mainly as a wrapper around data structures of the underlying library.
Definition at line 18 of file uv_type.hpp.
|
inlinevirtual |
Initializes the handle.
Reimplemented in uvw::async_handle, uvw::check_handle, uvw::fs_event_handle, uvw::fs_poll_handle, uvw::idle_handle, uvw::pipe_handle, uvw::poll_handle, uvw::prepare_handle, uvw::process_handle, uvw::signal_handle, uvw::tcp_handle, uvw::timer_handle, uvw::tty_handle, and uvw::udp_handle.
Definition at line 32 of file uv_type.hpp.
|
inlinenoexcept |
Gets the loop from which the resource was originated.
Definition at line 40 of file uv_type.hpp.
|
inlinenoexcept |
Gets the underlying raw data structure.
This function should not be used, unless you know exactly what you are doing and what are the risks.
Going raw is dangerous, mainly because the lifetime management of a loop, a handle or a request is in charge to the library itself and users should not work around it.
Definition at line 59 of file uv_type.hpp.
|
inlinenoexcept |
Gets the underlying raw data structure.
This function should not be used, unless you know exactly what you are doing and what are the risks.
Going raw is dangerous, mainly because the lifetime management of a loop, a handle or a request is in charge to the library itself and users should not work around it.
Definition at line 78 of file uv_type.hpp.