From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <Hilfinger@CS.Berkeley.EDU>, "'Daniel Jacobowitz'" <drow@false.org>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>,
<gdb-patches@sourceware.org>
Subject: RE: generic code duplication in Ada files
Date: Wed, 30 Jan 2008 11:39:00 -0000 [thread overview]
Message-ID: <000201c86322$bf093a30$3d1bae90$@u-strasbg.fr> (raw)
In-Reply-To: <200801292349.m0TNnVaV025063@tully.CS.Berkeley.EDU>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Paul Hilfinger
> Sent: Wednesday, January 30, 2008 12:50 AM
> To: Daniel Jacobowitz
> Cc: Joel Brobecker; gdb-patches@sourceware.org
> Subject: Re: generic code duplication in Ada files
>
>
> > Some of the things in Ada-specific code will be a mess to get into
> > common code, but IMO clearly worthwhile. For instance, a version of
> > symbol lookup which can return more than one symbol.
But pascal language has the same feature:
variables with the same name can coexist in different units,
either in the interface part (accessible to other units or the main program
if they reference the unit in the USES clause) or private
in the implementation part.
I am not sure the degugging information provided is
always precise enough to be able to sort out which variable
the compiler has chosen when a variable multiply defined is used.
Anyhow, getting the list of all public versions of
a given name would be great for pascal language too.
Pierre Muller
Pascal language support maintainer
next prev parent reply other threads:[~2008-01-30 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 22:41 Joel Brobecker
2008-01-29 22:51 ` Daniel Jacobowitz
2008-01-29 23:53 ` Paul Hilfinger
2008-01-30 11:39 ` Pierre Muller [this message]
2008-01-30 18:50 ` Joel Brobecker
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='000201c86322$bf093a30$3d1bae90$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=Hilfinger@CS.Berkeley.EDU \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.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