From: Ian Roxborough <irox@redhat.com>
To: Worik <worik@jungledrum.co.nz>
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: X-Ref Referres to for constructors
Date: Mon, 17 Sep 2001 17:43:00 -0000 [thread overview]
Message-ID: <3BA69B97.2C7F6917@redhat.com> (raw)
In-Reply-To: <3BA6883D.C91B81D2@jungledrum.co.nz>
Worik wrote:
> > Are they many (any) explicit calls being made to the constructor?
>
> No. The object in question is created like....
>
> class foo {
> ...
> };
>
> int main(){
> foo f;
> ...
> }
Ok, you aren't actually calling any constructors here. You are
creating an object (the constructor is called at run time but
not by you).
If you have had something like:
"foo::foo()"
or
"f.foo()" then it should show X-refs to constructors.
You can however perform X-Refs on classes which will show
you all the places that your object might be created (and hence the constructor
called).
Ian.
next prev parent reply other threads:[~2001-09-17 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 16:33 Worik
2001-09-17 16:47 ` Ian Roxborough
2001-09-17 17:43 ` Ian Roxborough [this message]
2001-09-18 0:47 ` Riccardo Cohen
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=3BA69B97.2C7F6917@redhat.com \
--to=irox@redhat.com \
--cc=sourcenav@sourceware.cygnus.com \
--cc=worik@jungledrum.co.nz \
/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).