From: Daniel Berlin <dberlin@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: Petr Sorfa <petrs@caldera.com>, <gdb@sources.redhat.com>,
Benjamin Kosnik <bkoz@redhat.com>,
Daniel Berlin <dan@dberlin.org>
Subject: Re: C++ nested classes, namespaces, structs, and compound statements
Date: Wed, 10 Apr 2002 12:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0204101531010.5447-100000@dberlin.org> (raw)
In-Reply-To: <npit6ze9v8.fsf@zwingli.cygnus.com>
On 10 Apr 2002, Jim Blandy wrote:
>
> Petr Sorfa <petrs@caldera.com> writes:
> > I've implemented FORTRAN95 MODULE support which is essentially
> > equivalent to namespaces (except you cannot have nested MODULEs.) I
> > treat it internally as a static class. For scoping issues I simply add
> > (in DWARF) the current local symbols to the MODULE to the local symbols
> > of the PROGRAM, CONTAINS, SUBROUTINE and FUNCTION scopes. A similar kind
> > of approach will allow nested C++ namespaces (flame bait comment.)
>
> I'm not sure I understand your implementation. (And I'm sure I don't
> understand FORTRAN...) So, when some program construct imports a
> module, you actually repeat the declarations for the imported module's
> contents in the debug info for the importing construct?
>
And if so, isn't the memory usage absurd for large programs?
next prev parent reply other threads:[~2002-04-10 19:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 20:42 Jim Blandy
2002-04-05 22:05 ` Daniel Berlin
2002-04-05 22:34 ` Daniel Jacobowitz
2002-04-05 23:49 ` Daniel Berlin
2002-04-06 7:18 ` Dan Kegel
2002-04-06 9:26 ` Gianni Mariani
2002-04-06 11:57 ` Daniel Berlin
2002-04-08 17:24 ` Jim Blandy
2002-04-08 17:03 ` Jim Blandy
2002-04-08 18:59 ` Daniel Jacobowitz
2002-04-09 18:35 ` Jim Blandy
2002-04-09 20:56 ` Daniel Jacobowitz
2002-04-12 15:08 ` Jim Blandy
2002-04-12 16:32 ` Daniel Jacobowitz
2002-04-08 17:19 ` Jim Blandy
2002-04-08 18:49 ` Daniel Jacobowitz
2002-04-10 10:31 ` Jim Blandy
2002-04-10 12:08 ` Daniel Jacobowitz
2002-04-12 13:58 ` Jim Blandy
2002-04-12 16:56 ` Daniel Jacobowitz
2002-04-16 12:08 ` Jim Blandy
2002-04-16 14:01 ` Daniel Jacobowitz
2002-04-16 14:52 ` Jim Blandy
2002-04-16 14:58 ` Daniel Jacobowitz
2002-04-06 6:31 ` Andrew Cagney
2002-04-06 7:58 ` Daniel Berlin
2002-04-08 0:59 ` Joel Brobecker
2002-04-08 2:01 ` Doubt in GDB SathisKanna k
2002-04-06 8:49 ` C++ nested classes, namespaces, structs, and compound statements Per Bothner
2002-04-08 16:29 ` Jim Blandy
2002-04-08 16:48 ` Daniel Jacobowitz
2002-04-09 6:55 ` Petr Sorfa
2002-04-10 10:34 ` Jim Blandy
2002-04-10 12:31 ` Daniel Berlin [this message]
2002-04-10 12:53 ` Petr Sorfa
2002-04-05 22:02 Michael Elizabeth Chastain
2002-04-05 22:13 ` Daniel Berlin
2002-04-05 22:30 ` Daniel Berlin
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=Pine.LNX.4.44.0204101531010.5447-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=bkoz@redhat.com \
--cc=dan@dberlin.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=petrs@caldera.com \
/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