SbByteBuffer(3)

πŸ“¦
version 4.0.10 Β· 4 versions
, in fedora 43, fedora 44

✨ SbByteBuffer ✨

okay bestie, welcome to the Coin manual, section 3 β€” yes we're in the library pages now, it's giving "grown-up Unix" and honestly? we ate. πŸŽ€

This one's about SbByteBuffer β€” literally just a little byte bucket. No cap. Let's get into it. πŸ¦‹


🌸 SYNOPSIS 🌸

πŸ’– Public Member Functions πŸ’–

Here's the whole lineup, fr fr. Every single one, no skipping, we don't do that here. πŸ‘‘

SbByteBuffer (const char *buffer)
SbByteBuffer (const SbByteBuffer &buffer)
SbByteBuffer (size_t size=0, const char *buffer=NULL)
SbByteBuffer (size_t size, const unsigned char *buffer)
SbBool isValid () const
size_t size () const
SbBool empty () const
const char & operator[] (size_t idx) const
SbByteBuffer & operator= (const SbByteBuffer &in)
SbBool operator== (const SbByteBuffer &that) const
SbByteBuffer & operator+= (const SbByteBuffer &buf)
void push (const SbByteBuffer &buf)
const char * constData () const
char * data ()
void makeUnique ()

🌈 Static Public Member Functions 🌈

static SbByteBuffer & invalidBuffer ()

πŸ’… Let's Talk About These Functions πŸ’…

So the vibe is: you got four constructors up top β€” one that takes a const char *, one that copies another SbByteBuffer (hello, copy constructor, you're iconic), one that takes a size_t size defaulting to 0 plus a const char *buffer defaulting to NULL, and one that takes a size_t size and a const unsigned char *buffer. Pick your fighter. 🫢

Then you got your little utility squad:

  • isValid() β€” returns an SbBool, tells you if this thing is actually valid. Vibe check, basically. βœ…
  • size() β€” returns a size_t, the size. She's honest, she's direct. πŸ’
  • empty() β€” returns an SbBool, is it empty or not. The audacity of a one-word answer. 😭
  • operator[] β€” takes a size_t idx and hands you back a const char &. Read-only peek energy. πŸ™ˆ
  • operator= β€” takes a const SbByteBuffer &in and returns an SbByteBuffer &. Assignment, but make it fashion. ✨
  • operator== β€” takes a const SbByteBuffer &that and returns an SbBool. Are you two the same? Inquiring minds need to know. πŸ‘€
  • operator+= β€” takes a const SbByteBuffer &buf, returns an SbByteBuffer &. Append szn. πŸ”₯
  • push() β€” takes a const SbByteBuffer &buf, returns void. Same energy as +=, different font. πŸ’œ
  • constData() β€” returns a const char *. Read-only access, hands off bestie. πŸŽ€
  • data() β€” returns a char *. Mutable access, go off. ⭐
  • makeUnique() β€” returns void. Makes it unique. She said "I'm not sharing." πŸ’…

And over in static land, we got:

  • invalidBuffer() β€” static, returns an SbByteBuffer &. It's the designated invalid one. When you need a buffer that is, respectfully, not it. πŸ’€
lowkey note: every single one of these is exactly as written up in the synopsis β€” no renaming, no merging, no inventing extra options. we keep the facts, we just make them cute. 🧚

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for Coin from the source code. (Yes, a robot wrote it. And it slayed. πŸ€–βœ¨)


Version 4.0.10 Β· Thu Jun 25 2026 00:00:00

okay that's the whole page bestie, mwah, go forth and buffer responsibly πŸ«ΆπŸ’–πŸŒΈ periodt πŸ¦‹

πŸ“¦ where this page comes from