Ryan Fleury

Fixed as of f48d8431c0b0940136a9756a34cf1fdb833bbf40.

Can you try this again on the latest commits? I've fixed some things w.r.t. global evaluation, and want to see if this is another manifestation of those bugs.

This is not the same test as original, as you're inside of `NS::Log::Trace` rather than `NS::Func`, so it isn't really testing what I was hoping to fix. But it did...

Great. As of 66b56789c6898049b994fdc7af5b2f99d53915ac, nested namespaces should now work, with the eval system's parser prioritizing more deeply nested namespace prefixes, then falling back on shallower ones. So inside of `Foo::Bar::Baz`,...

What version are you running? Can you see if the same issue persists on the newest commit in `master`? I've been shaking out some type info issues this weekend; the...

Thanks for the heads up! Yeah, I have noticed that before, although strangely enough, not *only* in RADDBG. So I'm not sure if it has to do with my own...

Whoa, yeah, that is weird & definitely a different issue - RADDBG is using totally the wrong type info (even though it is visualizing the correct type's name, `ArcEngine::ConstantBuffer`?). To...

That sounds like exactly the kind of C++ thing that we haven't tested very much, so glad we're hitting this now - I'll work on getting this all straightened out.

Great! Reproduced. I don't have the crazy `eastl::` types but I can confirm that the pure-virtual type is redirecting to a totally different type, for some reason... debugging now!

@MohitSethi99 As of my newest commits, the debugger should no longer display *incorrect* type info for pointers to pure-virtual classes, but it will *not* resolve base class pointers to their...