OUTGOINGDATAQUEUE_OUTGOINGRTPPKTLINK(3)

πŸ“¦
version 2.0.9 Β· 4 versions
, in debian trixie, ubuntu noble, ubuntu questing

πŸ’… NAME πŸ’…

OutgoingDataQueue::OutgoingRTPPktLink β€” bestie, it's a lil' linked-list node class from ccRTP's outgoing data queue, and it is literally holding your RTP packets together one pointer at a time 🫢


✨ SYNOPSIS ✨

Okay so first things first, you gotta pull in the header:

#include <oqueue.h>

🌸 Public Member Functions 🌸

OutgoingRTPPktLink (OutgoingRTPPkt *pkt, OutgoingRTPPktLink *p,
    OutgoingRTPPktLink *n)
~OutgoingRTPPktLink ()
OutgoingRTPPkt * getPacket ()
void setPacket (OutgoingRTPPkt *pkt)
OutgoingRTPPktLink * getPrev ()
void setPrev (OutgoingRTPPktLink *p)
OutgoingRTPPktLink * getNext ()
void setNext (OutgoingRTPPktLink *n)

πŸŽ€ Public Attributes πŸŽ€

OutgoingRTPPkt * packet
OutgoingRTPPktLink * prev
OutgoingRTPPktLink * next

🧚 Constructor & Destructor Documentation 🧚

Not me just dropping the two of these together because the manpage does the same β€” no extra tea spilled here, they're both marked [inline] and that's the whole story πŸ“Žβœ¨


πŸ‘‘ Member Function Documentation πŸ‘‘

Hands you back the next link in the chain, bestie. [inline] btw.

Gives you the OutgoingRTPPkt this link is carrying around like a little purse dog 🐢 [inline].

The link before this one, pls. [inline].

Sets what comes next. [inline], as always πŸ’…

Swaps in a new OutgoingRTPPkt for this node. [inline] πŸŽ€

Sets what came before. [inline] πŸ¦‹


🌈 Member Data Documentation 🌈

  • OutgoingRTPPktLink * OutgoingDataQueue::OutgoingRTPPktLink::next β€” the forward pointer, the "who's after me" of it all.
  • OutgoingRTPPkt* OutgoingDataQueue::OutgoingRTPPktLink::packet β€” the actual packet payload of the node, the main character fr.
  • OutgoingRTPPktLink* OutgoingDataQueue::OutgoingRTPPktLink::prev β€” the backward pointer, holding onto the past lowkey.

πŸ’œ Author πŸ’œ

Generated automatically by Doxygen for ccRTP from the source code. So like, no human wrote this, it's a robot's baby and we respect it 🫢

That's the whole page bestie, no cap, every single signature accounted for πŸ’–βœ¨ This one came from the ccRTP crew, living in section 3 of the Library Functions Manual β€” catch you in the next #include πŸŽ€πŸ’…πŸ¦‹

πŸ“¦ where this page comes from