SbName(3)
π SbName(3) π
okay bestie, welcome to the Coin manpage for SbName β yes that's the manual name, it's giving "section 3, library function", iconic. grab a boba, we're doing strings-by-reference today π§β¨
πΈ NAME πΈ
SbName β the SbName class stores strings by reference. periodt.
π¦ SYNOPSIS π¦
#include <Inventor/SbName.h>
π Public Member Functions
SbName (void)
SbName (const char *namestring)
SbName (const SbString &str)
SbName (const SbName &name)
~SbName ()
const char * getString (void) const
int getLength (void) const
int operator! (void) const
operator const char * (void) const
β¨ Static Public Member Functions
static SbBool isIdentStartChar (const char c)
static SbBool isIdentChar (const char c)
static SbBool isBaseNameStartChar (const char c)
static SbBool isBaseNameChar (const char c)
static const SbName & empty (void)
π Detailed Description π
The SbName class stores strings by reference.
So here's the tea: this class is what Coin uses for storing keywords, names and other strings. And the way it stores them? Identical strings are guaranteed to map to the same memory address (that's the address you get back from the SbName::getString() method). no cap, same string, same pointer, every single time π«
The main advantage of storing identical strings to the same memory address is that it simplifies comparison operations, and particularly when you're working with string data as keys in other data structures, like e.g. in hash (dictionary) tables. comparison becomes basically a pointer check and honestly? slay.
Apart from that, mapping identical strings to the same memory address can also save on memory resources, and provide runtime optimizations. String comparisons for SbName objects are very efficient, for instance. lowkey a flex.
β οΈ okay but listen, there's an aspect of usingSbNameinstances that it is important to be aware of: since strings are stored permanently, usingSbNameinstances in code where there is continually changing strings or the continual addition of new unique strings will in the end swamp memory resources. π so where possible, useSbStringinstances instead. fr fr, protect your RAM bestie.
See also
SbString
π Constructor & Destructor Documentation π
SbName::SbName (void )
This is the default constructor.
SbName::SbName (const char * namestring)
Constructor. Adds the namestring string to the name table. π
SbName::SbName (const SbString & str)
Constructor. Adds str to the name table.
SbName::SbName (const SbName & name)
Copy constructor.
SbName::~SbName ()
The destructor. bye bye π«Ά
π Member Function Documentation π
const char * SbName::getString (void ) const
This method returns pointer to character array for the name.
The returned memory pointer for the character string is guaranteed to be valid for the remaining life time of the process, even after all SbName instances referencing the string have been destructed. so likeβ¦ it outlives everything, main character energy honestly π
int SbName::getLength (void ) const
This method returns the number of characters in the name.
int SbName::operator! (void ) const
This unary operator results in FALSE if the SbName object is non-empty and TRUE if the SbName object is empty. An empty name contains a null-length string.
SbName::operator const char * (void ) const
This operator returns a pointer to the character array for the name string. It is intended for implicit use. Use SbName::getString() explicitly instead of this operator β it might be removed later. π¬ so like, don't get attached.
See also
const char * SbName::getString(void)
SbBool SbName::isIdentStartChar (const char c) [static]
This method checks if the c character is a valid identifier start character for a name.
See also
SbBool SbName::isIdentChar(const char c)
SbBool SbName::isIdentChar (const char c) [static]
This method checks if the c character is a valid character for a name.
See also
SbBool SbName::isIdentStartChar(const char c)
SbBool SbName::isBaseNameStartChar (const char c) [static]
Returns TRUE if the given character is valid for use as the first character of a name for an object derived from a class inheriting SoBase.
SoBase derived objects needs to be named in a manner which will not clash with the special characters reserved as tokens in the syntax rules of Open Inventor and VRML files.
Legal characters for the first character of an SoBase object name is underscore ("_") and any uppercase and lowercase alphabetic character from the ASCII character set (i.e. A-Z and a-z).
This method is not part of the original Open Inventor API.
See also
isBaseNameChar()
SbBool SbName::isBaseNameChar (const char c) [static]
Returns TRUE if the given character is valid for use in naming object instances of classes derived from SoBase.
SoBase derived objects needs to be named in a manner which will not clash with the special characters reserved as tokens in the syntax rules of Open Inventor and VRML files.
Legal characters to use for an SoBase object name is any character from the ASCII character set from and including character 33 (hex 0x21) to and including 126 (hex 0x7e), except single and double apostrophes, the plus sign and punctuation, backslash and the curly braces.
This method is not part of the original Open Inventor API.
See also
isBaseNameStartChar()
const SbName & SbName::empty (void ) [static]
Returns an empty-string SbName instance.
Since
- Coin 3.0
π Author π
Generated automatically by Doxygen for Coin from the source code.
and that's the whole page, bestie!! this one came from Coin version 4.0.10, dated Thu Jun 25 2026 00:00:00, and it lives at SbName(3). mwah, go forth and intern your strings π
πβ¨
π¦ where this page comes from
- fedora 43: Coin4-devel 4.0.10-1.fc43 Β· BSD-3-Clause AND GPL-3.0-or-later
- fedora 43: Coin4-devel 4.0.10-1.fc43 Β· BSD-3-Clause AND GPL-3.0-or-later
- fedora 44: Coin4-devel 4.0.10-1.fc44 Β· BSD-3-Clause AND GPL-3.0-or-later
- fedora 44: Coin4-devel 4.0.10-1.fc44 Β· BSD-3-Clause AND GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms