Enclosed file contains an excerpt from a bundle that is in development. The bundle exposes easy-to-use functions for managing versioned data. The data is housed within a specially-constructed superfile structure and there is a runtime check to ensure that the structure appears to be intact (via an ASSERT within the _NumGenerationsAvailable() function). I am unsure exactly what is causing this problem (module structure, INDEPENDENT usage, nested ASSERTs, etc.) so I'm including everything in the call chain.
The BWR executes one of the test functions for the bundle (DoTest) and works as-is. Note that the ASSERT within DoTest provides a full path of sorts to the function that is tested, explicitly providing all module names.
The function that is being tested is visible to DoTest. If you switch the comments around so that the next line is executed instead (so module names are not prefixed to the function name) then a warning appears at runtime:
The code does execute, though.
Additional oddity: In the Windows IDE, a syntax check of the version with the fully-qualified function name version shows "No Errors" but a syntax check of the other version shows no feedback whatsoever.