From: Marta Stojanovic <marta.stojanovic@nrc.ca>
To: sourcenav@sources.redhat.com
Subject: operator overloading and C++ parser
Date: Thu, 07 Jun 2001 07:00:00 -0000 [thread overview]
Message-ID: <3B1F892D.A952FE45@nrc.ca> (raw)
Hi all !
I searched the mailing list, but I didn't find this problem posted
(sorry for any duplicates). Here is the problem :
When there is an operator overloading in C++ code the parser does not
parse correctly the return types in following situations (in each of
these situations the return type will be int instead of the real return
type):
- when the return type is a class type returned by value (if it's
returned by reference, it parses it correctly)
- when the return type is a template argument type
- when the return type is a typedef.
I won't bother you with too many examples, here is just one (instead of
c4_Row there is int in the database) :
C++ code :
class c4_StringProp : public c4_Property
{
public:
....
c4_Row operator[] (const char*) const;
....
};
SN .md database entry :
{c4_StringProp operator[] 000674.011 metakit-2.3.4-29/include/mk4.h}
{674.41 0x4 {int} {const char *} {} {}}
I tested it on metakit source code
( http://sourceforge.net/projects/metakit/ ).
Kind regards,
Marta.
reply other threads:[~2001-06-07 7:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B1F892D.A952FE45@nrc.ca \
--to=marta.stojanovic@nrc.ca \
--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).