From: Doug Evans <xdje42@gmail.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] D: support reading modules from DWARF
Date: Sat, 18 Jul 2015 18:02:00 -0000 [thread overview]
Message-ID: <m3bnf91h1p.fsf@sspiff.org> (raw)
In-Reply-To: <CABOHX+cT+Zucmxn7jfuRF-hH-5scjiWGSf3wzDCZXXRfnN8-Tg@mail.gmail.com> (Iain Buclaw's message of "Mon, 13 Jul 2015 19:47:30 +0200")
Iain Buclaw <ibuclaw@gdcproject.org> writes:
> Hi,
>
> D uses modules (DW_TAG_module), but to separate the namespace of every
> source file. Modules can be imported into each other, either publicly
> or privately (DW_TAG_imported_module). Or declarations can be
> selectively imported or renamed (DW_TAG_imported_decl).
>
> This patch pretty much just extends the existing support for
> namespaces/modules in C++/Fortran/Java to include language_d too.
> However unlike Fortran/C++, the separator for qualified names is a
> single dot.
>
> This will need to be followed up with a patch to support looking up
> symbols in D module 'namespaces'. However I'm currently unsure
> whether to either extend cp-namespace.c, or to go ahead with my
> current fork (d-namespace.c), which copies only what's needed,
> adjusting for D-specific symbol import logic.
Hi.
Re: cp-namespace.c:
Hard to say without seeing the patch,
but having spent a lot of time cleaning up cp-namespace.c
I'm not fond of complicating it again to handle more languages.
So, and again I'd have to see the patch to be sure,
I'd say plan on going with d-namespace.c.
next prev parent reply other threads:[~2015-07-18 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 17:47 Iain Buclaw
2015-07-14 9:12 ` Pedro Alves
2015-07-18 18:02 ` Doug Evans [this message]
2015-07-20 7:11 ` Iain Buclaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bnf91h1p.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).