UT_ArrayStringMap.h File Reference

#include "UT_ArrayMap.h"
#include "UT_StringHolder.h"

Include dependency graph for UT_ArrayStringMap.h:

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes
class	UT_ArrayStringMap< ITEM_T >
struct	UT::DefaultClearer< UT_ArrayStringMap< ITEM_T > >

Namespaces
	UT

Macros
#define	__UT_ArrayStringMap_h__
#define	UT_STRINGREF_WRAPPER(return_type, name, qualifier)
#define	UT_STRINGREF_WRAPPER_RANGE(iterator_type, name, qualifier)

Macro Definition Documentation

#define __UT_ArrayStringMap_h__

Definition at line 14 of file UT_ArrayStringMap.h.

#define UT_STRINGREF_WRAPPER	(		return_type,
			name,
			qualifier
	)

Value:

SYS_FORCE_INLINE return_type name(const UT_StringRef &key) qualifier \
    { \
        return Parent::name(UTmakeUnsafeRef(key)); \
    }

We want methods like find() to take a const UT_StringRef& instead of a const UT_StringHolder& for the following reasons:

• This allows a const char* to be passed in without forcing a copy of the string.
• A UT_StringRef can be used without converting it to a UT_StringHolder (which hardens the string if necessary).
• A UT_StringHolder can still be directly passed in.

Definition at line 25 of file UT_ArrayStringMap.h.

#define UT_STRINGREF_WRAPPER_RANGE	(		iterator_type,
			name,
			qualifier
	)

Value:

SYS_FORCE_INLINE std::pair<iterator_type, iterator_type> \
    name(const UT_StringRef &key) qualifier \
    { \
        return Parent::name(UTmakeUnsafeRef(key)); \
    }

Specialization of the above macro for methods that return an iterator range, since something like std::pair<iterator, iterator> is interpreted as two arguments when being passed to a macro (due to the comma).

Definition at line 33 of file UT_ArrayStringMap.h.