This is the mail archive of the
mailing list for the GDB project.
Re: C++ nested classes, namespaces, structs, and compound statements
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Jim Blandy <jimb at redhat dot com>
- Cc: Petr Sorfa <petrs at caldera dot com>, <gdb at sources dot redhat dot com>,Benjamin Kosnik <bkoz at redhat dot com>, Daniel Berlin <dan at dberlin dot org>
- Date: Wed, 10 Apr 2002 15:31:21 -0400 (EDT)
- Subject: Re: C++ nested classes, namespaces, structs, and compound statements
On 10 Apr 2002, Jim Blandy wrote:
> Petr Sorfa <firstname.lastname@example.org> 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?