App - Utilities & Math
ThreadPool, Http client, G3D primitives, math functions, and URL parsers.
Subsystem Metrics
- Total Documented Functions:
1822 - Functions Exercised in Tests:
291 - Platform-Divergent Implementations:
200 - Component Source Files:
195
Source Files
View all 195 source files in this subsystem
| Source File | Path |
|---|---|
Analytics.h | App/include/util/Analytics.h |
AnimationId.h | App/include/util/AnimationId.h |
AsyncHttpCache.h | App/include/util/AsyncHttpCache.h |
AsyncHttpQueue.h | App/include/util/AsyncHttpQueue.h |
Average.h | App/include/util/Average.h |
Axes.h | App/include/util/Axes.h |
BiMultiMap.h | App/include/util/BiMultiMap.h |
BinaryString.h | App/include/util/BinaryString.h |
BrickColor.h | App/include/util/BrickColor.h |
CameraSubject.h | App/include/util/CameraSubject.h |
CellID.h | App/include/util/CellID.h |
CheatEngine.h | App/include/util/CheatEngine.h |
ClusterCellIterator.h | App/include/util/ClusterCellIterator.h |
Color.h | App/include/util/Color.h |
CompactEnum.h | App/include/util/CompactEnum.h |
ComputeProp.h | App/include/util/ComputeProp.h |
ConcurrencyValidator.h | App/include/util/ConcurrencyValidator.h |
ContentId.h | App/include/util/ContentId.h |
ControlledLRUCache.h | App/include/util/ControlledLRUCache.h |
DoubleEndedVector.h | App/include/util/DoubleEndedVector.h |
ExponentialRunningAverage.h | App/include/util/ExponentialRunningAverage.h |
Extents.h | App/include/util/Extents.h |
ExtentsInt32.h | App/include/util/ExtentsInt32.h |
Face.h | App/include/util/Face.h |
Faces.h | App/include/util/Faces.h |
FixedArray.h | App/include/util/FixedArray.h |
FixedSizeCircularBuffer.h | App/include/util/FixedSizeCircularBuffer.h |
Guid.h | App/include/util/Guid.h |
Handle.h | App/include/util/Handle.h |
HeapValue.h | App/include/util/HeapValue.h |
HeartbeatInstance.h | App/include/util/HeartbeatInstance.h |
HitTestFilter.h | App/include/util/HitTestFilter.h |
Http.h | App/include/util/Http.h |
HttpPlatformImpl.h | App/include/util/HttpPlatformImpl.h |
IHasLocation.h | App/include/util/IHasLocation.h |
IMetric.h | App/include/util/IMetric.h |
IndexArray.h | App/include/util/IndexArray.h |
IndexBox.h | App/include/util/IndexBox.h |
IndexedMesh.h | App/include/util/IndexedMesh.h |
IndexedTree.h | App/include/util/IndexedTree.h |
LRUCache.h | App/include/util/LRUCache.h |
Lcmrand.h | App/include/util/Lcmrand.h |
MD5Hasher.h | App/include/util/MD5Hasher.h |
Math.h | App/include/util/Math.h |
MovementHistory.h | App/include/util/MovementHistory.h |
Name.h | App/include/util/Name.h |
NavKeys.h | App/include/util/NavKeys.h |
NormalId.h | App/include/util/NormalId.h |
Object.h | App/include/util/Object.h |
ObscureValue.h | App/include/util/ObscureValue.h |
PV.h | App/include/util/PV.h |
PathInterpolatedCFrame.h | App/include/util/PathInterpolatedCFrame.h |
PhysicalProperties.h | App/include/util/PhysicalProperties.h |
PhysicsCoord.h | App/include/util/PhysicsCoord.h |
Profiling.h | App/include/util/Profiling.h |
ProgramMemoryChecker.h | App/include/util/ProgramMemoryChecker.h |
ProgressIndicator.h | App/include/util/ProgressIndicator.h |
ProtectedGeneric.h | App/include/util/ProtectedGeneric.h |
ProtectedString.h | App/include/util/ProtectedString.h |
Quaternion.h | App/include/util/Quaternion.h |
Rect.h | App/include/util/Rect.h |
Region2.h | App/include/util/Region2.h |
Region3.h | App/include/util/Region3.h |
Region3Int16.h | App/include/util/Region3Int16.h |
Rotation2d.h | App/include/util/Rotation2d.h |
RunStateOwner.h | App/include/util/RunStateOwner.h |
ScopedAssign.h | App/include/util/ScopedAssign.h |
ScriptInformationProvider.h | App/include/util/ScriptInformationProvider.h |
Selectable.h | App/include/util/Selectable.h |
Sound.h | App/include/util/Sound.h |
SoundChannel.h | App/include/util/SoundChannel.h |
SoundEffect.h | App/include/util/SoundEffect.h |
SoundService.h | App/include/util/SoundService.h |
SoundWorld.h | App/include/util/SoundWorld.h |
SpanningEdge.h | App/include/util/SpanningEdge.h |
SpanningNode.h | App/include/util/SpanningNode.h |
SpatialRegion.h | App/include/util/SpatialRegion.h |
SteppedInstance.h | App/include/util/SteppedInstance.h |
StlExtra.h | App/include/util/StlExtra.h |
StreamRegion.h | App/include/util/StreamRegion.h |
SurfaceType.h | App/include/util/SurfaceType.h |
SystemAddress.h | App/include/util/SystemAddress.h |
TextureId.h | App/include/util/TextureId.h |
ThreadPool.h | App/include/util/ThreadPool.h |
TouchType.h | App/include/util/TouchType.h |
URL.h | App/include/util/URL.h |
Units.h | App/include/util/Units.h |
UserInputBase.h | App/include/util/UserInputBase.h |
Utilities.h | App/include/util/Utilities.h |
VarInt.h | App/include/util/VarInt.h |
Vector3int32.h | App/include/util/Vector3int32.h |
Vector6.h | App/include/util/Vector6.h |
Velocity.h | App/include/util/Velocity.h |
base64.hpp | App/include/util/base64.hpp |
quadedge.h | App/include/util/quadedge.h |
Analytics.cpp | App/util/Analytics.cpp |
FileSystem.cpp | App/util/Android/FileSystem.cpp |
MachineIdUploader.cpp | App/util/Android/MachineIdUploader.cpp |
MemoryStats.cpp | App/util/Android/MemoryStats.cpp |
StringConv.cpp | App/util/Android/StringConv.cpp |
AsyncHttpQueue.cpp | App/util/AsyncHttpQueue.cpp |
Axes.cpp | App/util/Axes.cpp |
Base64BinaryInputStream.cpp | App/util/Base64BinaryInputStream.cpp |
Base64BinaryOutputStream.cpp | App/util/Base64BinaryOutputStream.cpp |
BrickColor.cpp | App/util/BrickColor.cpp |
CacheableContentProvider.cpp | App/util/CacheableContentProvider.cpp |
CameraSubject.cpp | App/util/CameraSubject.cpp |
Color.cpp | App/util/Color.cpp |
ContentFilter.cpp | App/util/ContentFilter.cpp |
ContentId.cpp | App/util/ContentId.cpp |
ContentProvider.cpp | App/util/ContentProvider.cpp |
ContentProviderJob.cpp | App/util/ContentProviderJob.cpp |
FileSystem.mm | App/util/Darwin/FileSystem.mm |
HttpCocoa.mm | App/util/Darwin/HttpCocoa.mm |
MachineIdUploader_OSX.cpp | App/util/Darwin/MachineIdUploader_OSX.cpp |
MemoryStats.cpp | App/util/Darwin/MemoryStats.cpp |
StringConv.cpp | App/util/Darwin/StringConv.cpp |
FileSystemDurango.cpp | App/util/Durango/FileSystemDurango.cpp |
ProgramMemoryChecker.cpp | App/util/Durango/ProgramMemoryChecker.cpp |
Extents.cpp | App/util/Extents.cpp |
Face.cpp | App/util/Face.cpp |
Faces.cpp | App/util/Faces.cpp |
FileSystemIndependent.cpp | App/util/FileSystemIndependent.cpp |
Guid.cpp | App/util/Guid.cpp |
Handle.cpp | App/util/Handle.cpp |
Hash.cpp | App/util/Hash.cpp |
HeartbeatInstance.cpp | App/util/HeartbeatInstance.cpp |
HitTest.cpp | App/util/HitTest.cpp |
HttpAsync.cpp | App/util/HttpAsync.cpp |
IndexBox.cpp | App/util/IndexBox.cpp |
IndexedMesh.cpp | App/util/IndexedMesh.cpp |
IndexedTree.cpp | App/util/IndexedTree.cpp |
LegacyContentTable.cpp | App/util/LegacyContentTable.cpp |
LuaWebService.cpp | App/util/LuaWebService.cpp |
MD5Hasher.cpp | App/util/MD5Hasher.cpp |
MachineIdUploader.cpp | App/util/MachineIdUploader.cpp |
MachineIdUploader_Windows.cpp | App/util/MachineIdUploader_Windows.cpp |
Math.cpp | App/util/Math.cpp |
MemoryStats.cpp | App/util/MemoryStats.cpp |
MemoryStatsCommon.cpp | App/util/MemoryStatsCommon.cpp |
MeshContentProvider.cpp | App/util/MeshContentProvider.cpp |
MovementHistory.cpp | App/util/MovementHistory.cpp |
Name.cpp | App/util/Name.cpp |
NormalId.cpp | App/util/NormalId.cpp |
PathInterpolatedCFrame.cpp | App/util/PathInterpolatedCFrame.cpp |
PhysicalProperties.cpp | App/util/PhysicalProperties.cpp |
Profiling.cpp | App/util/Profiling.cpp |
ProgramMemoryChecker.cpp | App/util/ProgramMemoryChecker.cpp |
ProtectedString.cpp | App/util/ProtectedString.cpp |
Quaternion.cpp | App/util/Quaternion.cpp |
RbxStringTable.cpp | App/util/RbxStringTable.cpp |
Rect.cpp | App/util/Rect.cpp |
Region2.cpp | App/util/Region2.cpp |
Region3.cpp | App/util/Region3.cpp |
Region3int32.cpp | App/util/Region3int32.cpp |
RobloxGoogleAnalytics.cpp | App/util/RobloxGoogleAnalytics.cpp |
RunStateOwner.cpp | App/util/RunStateOwner.cpp |
RunningAverage.cpp | App/util/RunningAverage.cpp |
Http.cpp | App/util/Shared/Http.cpp |
HttpCacheEntry.cpp | App/util/Shared/HttpCacheEntry.cpp |
HttpPlatformImpl.cpp | App/util/Shared/HttpPlatformImpl.cpp |
Sound.cpp | App/util/Sound.cpp |
SoundChannel.cpp | App/util/SoundChannel.cpp |
SoundEffect.cpp | App/util/SoundEffect.cpp |
SoundService.cpp | App/util/SoundService.cpp |
SpanningEdge.cpp | App/util/SpanningEdge.cpp |
SpanningNode.cpp | App/util/SpanningNode.cpp |
SpanningTree.cpp | App/util/SpanningTree.cpp |
SpatialRegion.cpp | App/util/SpatialRegion.cpp |
Statistics.cpp | App/util/Statistics.cpp |
SteppedInstance.cpp | App/util/SteppedInstance.cpp |
StreamRegion.cpp | App/util/StreamRegion.cpp |
TextureContentProvider.cpp | App/util/TextureContentProvider.cpp |
ThreadPool.cpp | App/util/ThreadPool.cpp |
UDim.cpp | App/util/UDim.cpp |
URL.cpp | App/util/URL.cpp |
UintSet.cpp | App/util/UintSet.cpp |
Units.cpp | App/util/Units.cpp |
MachOBaseAddr.mm | App/util/Unix/MachOBaseAddr.mm |
ProgramMemoryChecker.cpp | App/util/Unix/ProgramMemoryChecker.cpp |
UserInputBase.cpp | App/util/UserInputBase.cpp |
Utilities.cpp | App/util/Utilities.cpp |
Vector3int32.cpp | App/util/Vector3int32.cpp |
CheatEngine.cpp | App/util/Win/CheatEngine.cpp |
FileSystem.cpp | App/util/Win/FileSystem.cpp |
WinHeap.cpp | App/util/WinHeap.cpp |
WinHttp.cpp | App/util/WinHttp.cpp |
WinInet.cpp | App/util/WinInet.cpp |
XboxHttp2.cpp | App/util/XboxHttp2.cpp |
gpc.c | App/util/gpc.c |
md5.c | App/util/md5.c |
quadedge.cpp | App/util/quadedge.cpp |
rbxrandom.cpp | App/util/rbxrandom.cpp |
standardout.cpp | App/util/standardout.cpp |
xxhash.c | App/util/xxhash.c |
Function Reference
1. Points
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
public: Points();
| Property | Value |
|---|---|
| Return Type | public: |
| Modifiers | None |
| Source Location | App/include/util/Analytics.h:160 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Declaration or inline method for Points.
- Control Flow & Execution: Linear execution flow.
- Memory Management: Standard stack allocation.
- Concurrency & Thread Safety: Unsynchronized / single-threaded context.
- Error Handling & Invariants: Standard return value verification.
- State Mutation: Stateless or local modification.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on Points.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
2. setUserIdOverride
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void setUserIdOverride(const int id);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Analytics.h:164 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes setUserIdOverride within App - Utilities & Math. Coordinates interactions with format.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
format.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setUserIdOverride.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
3. addPoint
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void addPoint(const std::string& name, const rapidjson::Value& value, bool override = false);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Analytics.h:169 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes addPoint within App - Utilities & Math. Coordinates interactions with Point, insert, erase.
- Control Flow & Execution: Conditional branching.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
Point,insert,erase. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on addPoint.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
4. report
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void report(const std::string& resource, int throttleHundredthsPercentage, bool blocking = false);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Analytics.h:181 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes report within App - Utilities & Math. Coordinates interactions with empty, reportPointsV2, reportPoints, clear.
- Control Flow & Execution: Conditional branching.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
empty,reportPointsV2,reportPoints,clear. - External Library Dependencies:
InfluxDB Metrics Ingestion Client.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on report.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
5. getPoints
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
boost::unordered_set<Point>& getPoints() const;
| Property | Value |
|---|---|
| Return Type | boost::unordered_set<Point>& |
| Modifiers | const |
| Source Location | App/include/util/Analytics.h:193 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getPoints within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getPoints.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
6. isActive
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
bool isActive() const;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/util/AnimationId.h:13 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes isActive within App - Utilities & Math. Coordinates interactions with toString, substr.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
- Key Internal Calls:
toString,substr.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isActive.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
7. nullAnimation
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
AnimationId nullAnimation();
| Property | Value |
|---|---|
| Return Type | AnimationId |
| Modifiers | static |
| Source Location | App/include/util/AnimationId.h:15 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes nullAnimation within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on nullAnimation.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
8. getRequestedUrls
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
shared_ptr<const Reflection::ValueArray> getRequestedUrls();
| Property | Value |
|---|---|
| Return Type | shared_ptr<const Reflection::ValueArray> |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:16 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getRequestedUrls within App - Utilities & Math. Coordinates interactions with result, lock, begin, end. Employs reference-counted heap object ownership (boost::shared_ptr).
- Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
- Memory Management: Reference-counted heap object ownership (boost::shared_ptr).
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
result,lock,begin,end,isHttp,push_back,toString. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getRequestedUrls.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
9. setCacheSize
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void setCacheSize(int count);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:41 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes setCacheSize within App - Utilities & Math. Coordinates interactions with lock, resize.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,resize. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setCacheSize.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
10. findCacheItem
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
bool findCacheItem(const std::string& id, CachedContent* result);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:47 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes findCacheItem within App - Utilities & Math. Coordinates interactions with lock, fetch.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,fetch. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on findCacheItem.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
11. removeCacheItem
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void removeCacheItem(const std::string& id);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:53 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes removeCacheItem within App - Utilities & Math. Coordinates interactions with lock, remove.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,remove. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on removeCacheItem.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
12. invalidateCacheItemOrFailure
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void invalidateCacheItemOrFailure(const std::string& id);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:58 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes invalidateCacheItemOrFailure within App - Utilities & Math. Coordinates interactions with lock, remove, end, begin.
- Control Flow & Execution: Iterative loop processing, Conditional branching.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,remove,end,begin,erase. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on invalidateCacheItemOrFailure.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
13. insertCacheItem
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void insertCacheItem(const std::string& id, const CachedContent& result);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:79 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes insertCacheItem within App - Utilities & Math. Coordinates interactions with lock, insert.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,insert. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on insertCacheItem.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
14. renameCacheItem
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void renameCacheItem(const std::string& id, const std::string& newId);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:84 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes renameCacheItem within App - Utilities & Math. Coordinates interactions with lock, fetch, remove, insert.
- Control Flow & Execution: Conditional branching.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,fetch,remove,insert. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on renameCacheItem.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
15. clearCache
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void clearCache();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:95 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes clearCache within App - Utilities & Math. Coordinates interactions with lock, clear.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock,clear. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on clearCache.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
16. printContentNames
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void printContentNames();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpCache.h:107 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes printContentNames within App - Utilities & Math. Coordinates interactions with lock.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lock. - External Library Dependencies:
Boost C++ Libraries.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on printContentNames.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
17. setCachePolicy
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void setCachePolicy(const HttpCache::Policy policy);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpQueue.h:47 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes setCachePolicy within App - Utilities & Math.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setCachePolicy.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
18. getAvgTimeInQueue
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
double getAvgTimeInQueue();
| Property | Value |
|---|---|
| Return Type | double |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpQueue.h:69 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getAvgTimeInQueue within App - Utilities & Math. Coordinates interactions with value.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
value.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getAvgTimeInQueue.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
19. getAvgRequestCompleteTime
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
double getAvgRequestCompleteTime();
| Property | Value |
|---|---|
| Return Type | double |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpQueue.h:70 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getAvgRequestCompleteTime within App - Utilities & Math. Coordinates interactions with value.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
value.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getAvgRequestCompleteTime.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
20. getNumSlowRequests
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
int getNumSlowRequests();
| Property | Value |
|---|---|
| Return Type | int |
| Modifiers | None |
| Source Location | App/include/util/AsyncHttpQueue.h:71 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getNumSlowRequests within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getNumSlowRequests.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
21. registerContent
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void registerContent(const std::string& url, shared_ptr<const std::string> response, shared_ptr<const std::string> filename);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/util/AsyncHttpQueue.h:74 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Declaration or inline method for registerContent.
- Control Flow & Execution: Linear execution flow.
- Memory Management: Standard stack allocation.
- Concurrency & Thread Safety: Unsynchronized / single-threaded context.
- Error Handling & Invariants: Standard return value verification.
- State Mutation: Stateless or local modification.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on registerContent.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
22. sample
Status: 🧪 Tested | 🌐 Cross-Platform Uniform
void sample(T value, bool advanceBuffer = true);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Average.h:20 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes sample within App - Utilities & Math.
- Control Flow & Execution: Conditional branching.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
This function is exercised in 1 test case(s):
PathfindingTest::PathfindingStress(App.UnitTest/PathfindingTest.cpp:48)- Usage Pattern:
Direct Call - Callsite Snippet:
runAverage.sample(RakNet::GetTime() - start_test_time);
- Usage Pattern:
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
23. getAverage
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
T getAverage() const;
| Property | Value |
|---|---|
| Return Type | T |
| Modifiers | const |
| Source Location | App/include/util/Average.h:28 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getAverage within App - Utilities & Math.
- Control Flow & Execution: Iterative loop processing, Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getAverage.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
24. size
Status: 🧪 Tested | ⚠️ Platform Divergent
size_t size() const;
| Property | Value |
|---|---|
| Return Type | size_t |
| Modifiers | const |
| Source Location | App/include/util/Average.h:37 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes size within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
How it is Used in Tests
This function is exercised in 59 test case(s):
Instance::LockUnlockDeprecated(App.UnitTest/Instance.cpp:186)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_REQUIRE_EQUAL(result->values.size(), 1) - Callsite Snippet:
BOOST_REQUIRE_EQUAL(result->values.size(), 1);
- Usage Pattern:
WebSerializer::TestWebSerializerList(App.UnitTest/WebSerializerTest.cpp:12)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(newValueCollection->size() == valueCollection->size()) - Callsite Snippet:
BOOST_CHECK(newValueCollection->size() == valueCollection->size());
- Usage Pattern:
WebSerializer::TestWebSerializerTable(App.UnitTest/WebSerializerTest.cpp:57)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(newValueMap->size() == valueMap->size()) - Callsite Snippet:
BOOST_CHECK(newValueMap->size() == valueMap->size());
- Usage Pattern:
WebSerializer::TestWebSerializerInstance(App.UnitTest/WebSerializerTest.cpp:115)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(newValue.get<shared_ptr<Instance> >()->getChildren()->size() == 3) - Callsite Snippet:
BOOST_CHECK(newValue.get<shared_ptr<Instance> >()->getChildren()->size() == 3);
- Usage Pattern:
Behavioral Differences Across Code Files
Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/p2p.h.
- Alternative Implementation Files:
XboxClient/p2p.h
25. getValue
Status: 🧪 Tested | 🌐 Cross-Platform Uniform
T& getValue(size_t index) const;
| Property | Value |
|---|---|
| Return Type | T& |
| Modifiers | const const |
| Source Location | App/include/util/Average.h:41 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes getValue within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
How it is Used in Tests
This function is exercised in 5 test case(s):
Xml::Parse(App.UnitTest/XmlElement.cpp:12)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_REQUIRE(node->getValue(value)),BOOST_REQUIRE(attribute->getValue(value)) - Callsite Snippet:
BOOST_REQUIRE(node->getValue(value));
- Usage Pattern:
Xml::StringToInt(App.UnitTest/XmlElement.cpp:42)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(element.getValue(i)),BOOST_CHECK(!element2.getValue(i)),BOOST_CHECK(!element3.getValue(i)) - Callsite Snippet:
BOOST_CHECK(element.getValue(i));
- Usage Pattern:
ModuleScriptTest::ReturnStatefulClosure(App.UnitTest/ModuleScriptTest.cpp:63)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK_EQUAL(16, Instance::fastDynamicCast<IntValue>(inst16)->getValue()) - Callsite Snippet:
BOOST_CHECK_EQUAL(16, Instance::fastDynamicCast<IntValue>(inst16)->getValue());
- Usage Pattern:
ModuleScriptTest::SharedLoadResult(App.UnitTest/ModuleScriptTest.cpp:108)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK_EQUAL(14, Instance::fastDynamicCast<IntValue>(inst14)->getValue()) - Callsite Snippet:
BOOST_CHECK_EQUAL(14, Instance::fastDynamicCast<IntValue>(inst14)->getValue());
- Usage Pattern:
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
26. resetValues
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void resetValues(const T& value);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Average.h:45 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes resetValues within App - Utilities & Math.
- Control Flow & Execution: Iterative loop processing.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on resetValues.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
27. resetValues
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void resetValues(size_t samplesNew, const T& value);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Average.h:51 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes resetValues within App - Utilities & Math. Coordinates interactions with resize.
- Control Flow & Execution: Iterative loop processing.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
resize.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on resetValues.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
28. clear
Status: 🧪 Tested | 🌐 Cross-Platform Uniform
void clear();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/Axes.h:18 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes clear within App - Utilities & Math.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
This function is exercised in 2 test case(s):
signals::AssignmentOperator(Base.UnitTest/signals.cpp:350)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_CHECK_EQUAL(result, "Hello"),BOOST_CHECK_EQUAL(result, "") - Callsite Snippet:
result.clear();
- Usage Pattern:
signals::ReentrantResetScopedConnection(Base.UnitTest/signals.cpp:413)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_CHECK_EQUAL(result, "Reset"),BOOST_CHECK_EQUAL(result, "HelloReset#") - Callsite Snippet:
result.clear();
- Usage Pattern:
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
29. pairInMap
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
bool pairInMap(const Left& left, const Right& right);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | App/include/util/BiMultiMap.h:17 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes pairInMap within App - Utilities & Math. Coordinates interactions with lower_bound, upper_bound.
- Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
lower_bound,upper_bound.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on pairInMap.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
30. insertPair
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void insertPair(const Left& left, const Right& right);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/BiMultiMap.h:27 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes insertPair within App - Utilities & Math. Coordinates interactions with RBXASSERT_SLOW, pairInMap, insert, make_pair.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
RBXASSERT_SLOW,pairInMap,insert,make_pair.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on insertPair.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
31. removePair
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void removePair(const Left& left, const Right& right);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/BiMultiMap.h:32 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes removePair within App - Utilities & Math. Coordinates interactions with RBXASSERT_SLOW, pairInMap, lower_bound, upper_bound.
- Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
RBXASSERT_SLOW,pairInMap,lower_bound,upper_bound,erase,RBXASSERT.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on removePair.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
32. empty
Status: 🧪 Tested | 🌐 Cross-Platform Uniform
bool empty() const;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/util/BiMultiMap.h:45 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes empty within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
How it is Used in Tests
This function is exercised in 6 test case(s):
LuaDebugger::FlatDataSerialization(App.UnitTest/LuaDebugger.cpp:139)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(binaryDataStreamOriginal.str().empty() != true) - Callsite Snippet:
BOOST_CHECK(binaryDataStreamOriginal.str().empty() != true);
- Usage Pattern:
LuaDebugger::NestedDataSerialization(App.UnitTest/LuaDebugger.cpp:211)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(binaryDataStreamOriginal.str().empty() != true) - Callsite Snippet:
BOOST_CHECK(binaryDataStreamOriginal.str().empty() != true);
- Usage Pattern:
URLParser::Split(App.UnitTest/URLParserTest.cpp:7)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(url.query().empty()) - Callsite Snippet:
BOOST_CHECK(url.query().empty());
- Usage Pattern:
URLParser::Invalid(App.UnitTest/URLParserTest.cpp:128)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_CHECK(!url.isValid()),BOOST_CHECK_EQUAL(url.asString(), "") - Callsite Snippet:
BOOST_CHECK(url.scheme().empty());
- Usage Pattern:
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
33. emptyLeft
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
bool emptyLeft(const Left& left) const;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/util/BiMultiMap.h:49 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes emptyLeft within App - Utilities & Math. Coordinates interactions with return, lower_bound, upper_bound.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
- Key Internal Calls:
return,lower_bound,upper_bound.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on emptyLeft.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
34. visitEachLeft
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
void visitEachLeft(const Left& left, const Func& func) const;
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | inline const |
| Source Location | App/include/util/BiMultiMap.h:53 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes visitEachLeft within App - Utilities & Math. Coordinates interactions with lower_bound, upper_bound, func.
- Control Flow & Execution: Iterative loop processing.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
- Key Internal Calls:
lower_bound,upper_bound,func.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on visitEachLeft.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
35. BinaryString
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
public: BinaryString();
| Property | Value |
|---|---|
| Return Type | public: |
| Modifiers | None |
| Source Location | App/include/util/BinaryString.h:9 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Declaration or inline method for BinaryString.
- Control Flow & Execution: Linear execution flow.
- Memory Management: Standard stack allocation.
- Concurrency & Thread Safety: Unsynchronized / single-threaded context.
- Error Handling & Invariants: Standard return value verification.
- State Mutation: Stateless or local modification.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on BinaryString.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
36. internalValue
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
: internalValue(value);
| Property | Value |
|---|---|
| Return Type | : |
| Modifiers | None |
| Source Location | App/include/util/BinaryString.h:15 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Declaration or inline method for internalValue.
- Control Flow & Execution: Linear execution flow.
- Memory Management: Standard stack allocation.
- Concurrency & Thread Safety: Unsynchronized / single-threaded context.
- Error Handling & Invariants: Standard return value verification.
- State Mutation: Stateless or local modification.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on internalValue.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
37. value
Status: 🧪 Tested | 🌐 Cross-Platform Uniform
std::string& value() const;
| Property | Value |
|---|---|
| Return Type | std::string& |
| Modifiers | const const |
| Source Location | App/include/util/BinaryString.h:18 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes value within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Immutable / read-only operation (const member method; does not alter object state).
How it is Used in Tests
This function is exercised in 2 test case(s):
StreamRegionTest::RegionIdCreateTest(App.UnitTest/StreamRegionTest.cpp:80)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK_EQUAL(Vector3int32(-1, 0, 0), regionId.value()) - Callsite Snippet:
BOOST_CHECK_EQUAL(Vector3int32(-1, 0, 0), regionId.value());
- Usage Pattern:
SpatialRegionTest::RegionContainingVoxel(App.UnitTest/SpatialRegionTest.cpp:9)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK_EQUAL(Vector3int16::zero(), id.value()),BOOST_CHECK_EQUAL(Vector3int16::zero(), id.value()),BOOST_CHECK_EQUAL(Vector3int16(-1,-1,-1), id.value()),BOOST_CHECK_EQUAL(Vector3int16(-1,-1,-1), id.value()) - Callsite Snippet:
BOOST_CHECK_EQUAL(Vector3int16::zero(), id.value());
- Usage Pattern:
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
38. set
Status: 🧪 Tested | 🌐 Cross-Platform Uniform
void set(const char* buffer, unsigned int size);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/util/BinaryString.h:23 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes set within App - Utilities & Math. Coordinates interactions with assign.
- Control Flow & Execution: Direct sequential execution.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
assign.
How it is Used in Tests
This function is exercised in 19 test case(s):
ReplicatorGcJobTest::RegionRemovalIdsKeepFirstSeenOrder(App.UnitTest/ReplicatorGcJobTest.cpp:34)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_CHECK(ids.insert(first)),BOOST_CHECK(ids.insert(second)) - Callsite Snippet:
first.scope.set("stream-out-test-a");
- Usage Pattern:
ReplicatorGcJobTest::MovingPartOutsideOfStreamedAreaCausesItToBeGced(App.UnitTest/ReplicatorGcJobTest.cpp:98)- Usage Pattern:
Performance Benchmark - Assertions Checked:
BOOST_REQUIRE(clientDm->getWorkspace()->findFirstChildByName("BasePlate")),BOOST_REQUIRE(clientDm->getWorkspace()->findFirstChildByName("ToStreamOut")) - Callsite Snippet:
Workspace::prop_StreamingEnabled.set(serverDm->getWorkspace(), true);
- Usage Pattern:
ReplicatorGcJobTest::MovingPartAndItsParentOutsideOfStreamedAreaShouldNotRemoveThePartTwice(App.UnitTest/ReplicatorGcJobTest.cpp:195)- Usage Pattern:
Performance Benchmark - Assertions Checked:
BOOST_REQUIRE(clientDm->getWorkspace()->findFirstChildByName("BasePlate")),BOOST_REQUIRE(parent) - Callsite Snippet:
Workspace::prop_StreamingEnabled.set(serverDm->getWorkspace(), true);
- Usage Pattern:
ReplicatorGcJobTest::ReparentingToGcedPartCausesInstanceToLeave(App.UnitTest/ReplicatorGcJobTest.cpp:305)- Usage Pattern:
Performance Benchmark - Assertions Checked:
BOOST_REQUIRE(clientDm->getWorkspace()->findFirstChildByName("Inside")),BOOST_REQUIRE(clientDm->getWorkspace()->findFirstChildByName("Outside")) - Callsite Snippet:
Workspace::prop_StreamingEnabled.set(serverDm->getWorkspace(), true);
- Usage Pattern:
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
39. brickWhite
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickWhite();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:255 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickWhite within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickWhite.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
40. brickGray
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickGray();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:259 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickGray within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickGray.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
41. brickDarkGray
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickDarkGray();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:263 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickDarkGray within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickDarkGray.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
42. brickBlack
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickBlack();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:267 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickBlack within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickBlack.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
43. brickRed
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickRed();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:271 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickRed within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickRed.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
44. brickYellow
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickYellow();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:275 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickYellow within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickYellow.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
45. brickGreen
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickGreen();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:279 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickGreen within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickGreen.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
46. baseplateGreen
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor baseplateGreen();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:283 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes baseplateGreen within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on baseplateGreen.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
47. brickBlue
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor brickBlue();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:287 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes brickBlue within App - Utilities & Math.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
How it is Used in Tests
No dedicated unit test case directly exercises this function by name.
This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on brickBlue.
Behavioral Differences Across Code Files
This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.
48. defaultColor
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
BrickColor defaultColor();
| Property | Value |
|---|---|
| Return Type | BrickColor |
| Modifiers | inline static |
| Source Location | App/include/util/BrickColor.h:291 |
| Subsystem | App - Utilities & Math |
How it Works Internally
Executes defaultColor within App - Utilities & Math. Coordinates interactions with BrickColor.
- Control Flow & Execution: Explicit result return.
- Memory Management: Stack-based automatic variable allocation.
- Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
- Error Handling & Invariants: Relies on standard return codes and caller validation.
- State Mutation: Pure computational logic or modifies passed-in parameters/references.
- Key Internal Calls:
BrickColor.