public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: alex.shneer@verizon.com
To: Ian Roxborough <irox@redhat.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: cross references of static functions
Date: Wed, 10 Jan 2001 13:47:00 -0000	[thread overview]
Message-ID: <852569D0.00764DD5.00@smtpsrv1.bigyellow.com> (raw)

Can you think of any possible workarounds or patches for 4.5.2 that could
solve this or will it be fixed in the next version?

There are similar scope management problems in the COBOL parser.
I thought to borrow ideas from C++ parser to patch the cobol parser: no
luck here, obviously.





Ian Roxborough <irox@redhat.com> on 01/10/2001 04:23:01 PM

To:   alex.shneer@verizon.com
cc:   sourcenav@sources.redhat.com
Subject:  Re: cross references of static functions





This sounds like bad scope management.  One of the many parser
problems that needs to be solved.  Once we add support for things
like namespaces and innerclasses, we should have way better scope
management (well, really we need to improve scope management
inorder to add namespace and innerclass support).

Ian.


alex.shneer@verizon.com wrote:
>
> Hi,
> can anybody tell why cross reference window shows that both func1 and
func2
>  are referenced by static_func,
> no matter wich one we choose: one defined in the static1.c or one defined
> in static2.c?
>
> static1.c:
> --------------------------------------
> static static_func()
> {
>    func1();
> }
> --------------------------------------
> static2.c
> --------------------------------------
> static static_func ()
> {
>    func2();
> }
> ---------------------------------------




             reply	other threads:[~2001-01-10 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 13:47 alex.shneer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-18  6:25 alex.shneer
2001-01-18  7:26 ` Khamis Abuelkomboz
2001-01-18  0:53 Khamis Abuelkomboz
2001-01-10 13:01 alex.shneer
2001-01-10 13:23 ` Ian Roxborough

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=852569D0.00764DD5.00@smtpsrv1.bigyellow.com \
    --to=alex.shneer@verizon.com \
    --cc=irox@redhat.com \
    --cc=sourcenav@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).