https://issues.dlang.org/show_bug.cgi?id=18882
Rainer Schuetze changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=18882
Walter Bright changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
https://issues.dlang.org/show_bug.cgi?id=18882
Walter Bright changed:
What|Removed |Added
Keywords||symdeb
CC|
https://issues.dlang.org/show_bug.cgi?id=18882
--- Comment #4 from Rainer Schuetze ---
The debug info contains the "pretty" name, i.e. the fully qualified name, even
for extern(C++) symbols. Otherwise you would have to guess the linkage and type
as it is part of the mangled name.
What could be p
https://issues.dlang.org/show_bug.cgi?id=18882
--- Comment #3 from Manu ---
Hmm... yeah, that's unfortunate.
I don't understand why it's hard to resolve the name. It's extern(C++), and it
has no namespace supplied, so the correct symbol name should just be the
mangled name, with no scope or anyt
https://issues.dlang.org/show_bug.cgi?id=18882
--- Comment #2 from Rainer Schuetze ---
See also issue 11024: there is no information about imports in the debug
informations so you don't know which symbols are visible in the current scope
and what their qualified name is.
In D functions, the qual
https://issues.dlang.org/show_bug.cgi?id=18882
--- Comment #1 from Manu ---
Perhaps it's the extern(C++) that's the problem?
That would explain why I have debug problems a lot.
--
https://issues.dlang.org/show_bug.cgi?id=18882
Manu changed:
What|Removed |Added
Assignee|nob...@puremagic.com|r.sagita...@gmx.de
--
