ws_match_res(3)

πŸ“¦
version 2.3.2 Β· 3 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– ws_match_res πŸ’–

okay bestie, so like β€” this is ws_match_res, a lil struct from the Library Functions Manual section, and it lives over in cwrapper.h. she's small, she's simple, she's giving "three doubles and a dream" energy. 🌸


✨ SYNOPSIS ✨

🌈 Public Attributes

double res1
double res2
double flow

that's it. that's the whole struct. three public double members, no secrets, no gatekeeping, no cap. πŸ’…


πŸ¦‹ Detailed Description πŸ¦‹

so ws_match_res is literally just a container, right? and she is defined at line 152 of file cwrapper.h. iconic behavior honestly. mark it, screenshot it, whatever β€” line 152, cwrapper.h. πŸ’–


πŸŽ€ Member Data Documentation πŸŽ€

okay now let's do a lil roll call for the members, one by one, because they each get their own line in the source and we respect them for that. πŸ‘‘

  • double ws_match_res::flow β€” the third one alphabetically but the last one in the file, defined at line 155 of file cwrapper.h. she said "I'll go last, I don't mind." 🫢
  • double ws_match_res::res1 β€” the firstborn member, defined at line 153 of file cwrapper.h. yes she comes right after the struct itself, main character energy fr fr. ⭐
  • double ws_match_res::res2 β€” the middle child, defined at line 154 of file cwrapper.h. sandwiched between her two siblings, lowkey tragic, highkey fine. πŸ’œ
note bestie: every single one of these is a plain double β€” no fancy types, no pointers, no arrays, just vibes and floating point. πŸ“

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for IsoSpec from the source code.

not a human. not a poet. a documentation generator. and honestly? she ate. πŸ€–βœ¨


that's the whole page bestie, no notes, it's giving short and sweet and fully complete. πŸ’–πŸ¦‹πŸŒΈ

signing off from the IsoSpec era β€” this page brought to you by Doxygen, auto-generated straight from the source code, and stamped with the ws_match_res(3) footer so you know exactly which manual section you're in. bye pookie, go read the actual header file πŸ’…πŸŽ€

πŸ“¦ where this page comes from