This is the mail archive of the
archer@sourceware.org
mailing list for the Archer project.
Re: Interpretation of DW_AT_external
On Mon, Aug 25, 2008 at 02:03:40PM -0400, Sami Wagiaalla wrote:
>> we just build up the names ourselves instead of by the demangler.
>
> Gotcha... Are there mechanisms in place to handling the following situation:
>
> namespace A{
> namespace B{
> int ab;
> }
>
> void func1{
> B::ab;
> }
> }
>
> void func2{
> A::B::ab;
> }
>
> If the user types print B::ab in func1 and A::B::ab in func2 will both be
> work correctly ?
Yes, it should. You can follow the lookup algorithm into
cp-namespace.c; it even handles "using" statements.
>> I agree that doing it block-wise would be superior.
>
> Should I continue with the block quest then ?.. Do you think that we will
> run into issues in the future with storing the fully qualified names ?
It's slow to construct the names, and pretty wasteful. But changing
this is going to be complicated :-(
--
Daniel Jacobowitz
CodeSourcery