__GNU_CXX::_RELATIVE_POINTER_IMPL(3cxx)

🌸 NAME 🌸

okay so bestie, welcome to the man page for __gnu_cxx::_Relative_pointer_impl< _Tp > — manual section 3cxx, no cap. It’s a storage policy for use with _Pointer_adapter<> which stores the pointer’s address as an offset value which is relative to its own address. 💅

✨ SYNOPSIS ✨

the include is giving one line and one line only:

#include <pointer.h>

💖 Public Types 💖

• typedef _Tp element_type — yup, that’s the public type, exactly as written. 🎀

🫶 Public Member Functions 🫶

• _Tp * get () const — the getter signature, untouched and iconic. ✨
• bool operator< (const _Relative_pointer_impl &__rarg) const — the less-than operator signature, exactly as listed. 💜
• bool operator== (const _Relative_pointer_impl &__rarg) const — the equality operator signature, exactly as listed. 🦋
• void set (_Tp *__arg) — the setter signature, exactly as listed. 🌸

🦋 Detailed Description 🦋

template<typename _Tp> — class __gnu_cxx::_Relative_pointer_impl< _Tp >. periodt. 👑

okay so here’s the actual vibe: it’s a storage policy for use with _Pointer_adapter<> which stores the pointer’s address as an offset value which is relative to its own address. It’s lowkey built for shared-memory situations. 🫶

This is intended for pointers within shared memory regions which might be mapped at different addresses by different processes. 🌈

For null pointers, a value of 1 is used. And yes, 0 is legitimate sometimes for nodes in circularly linked lists. (Not me remembering that detail, but okay.) This value was chosen as the least likely to generate an incorrect null, As there is no reason why any normal pointer would point 1 byte into its own pointer address. fr fr 💀

💜 Author 💜

The author line says: Generated automatically by Doxygen for libstdc++ from the source code. iconic. 🎀

---

okay bestie, that’s the whole page! 🫶 The original footer’s source/version and date stamp is libst__gnu_cxx::_Rel...ter_impl< _Tp >(3cxx), so that’s the cute sign-off instead of a copied footer. bye! 💖