From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: same-name vars from different scopes
Date: Fri, 19 Mar 2010 01:54:00 -0000 [thread overview]
Message-ID: <m3eijhyt30.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BA2B416.6000708@vmware.com> (Michael Snyder's message of "Thu, 18 Mar 2010 16:15:34 -0700")
>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
Michael> Is there a syntax for printing/using a static variable from a
Michael> different module, even though it's eclipsed by a more-local
Michael> variable of the same name?
According the node Variables in the manual, this should work:
print 'file.c'::global
Surprisingly, I don't think I have ever actually done this.
There's no syntax for printing a local variable which is hidden by a
more inner definition.
Tom
next prev parent reply other threads:[~2010-03-19 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 23:15 Michael Snyder
2010-03-19 1:54 ` Tom Tromey [this message]
2010-03-19 5:28 ` Joel Brobecker
2010-03-19 17:54 ` Tom Tromey
2010-03-19 17:41 ` Michael Snyder
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=m3eijhyt30.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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