public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Drexler <drexler@informatik.uni-erlangen.de>
To: sourcenav@sources.redhat.com
Subject: replacing "defines"
Date: Thu, 21 Feb 2002 13:59:00 -0000	[thread overview]
Message-ID: <20020221210532.B14796@faui5pc48.informatik.uni-erlangen.de> (raw)

Dear mailinglist members,

I started to use SourceNavigator only a few days before and it is a great and
easy to use software. But we encountered some problems with the substituion of
'#defines'.

We have a huge sofware project here at our chair which I wanted to put
under the control of SourceNavigator. One Problem is that we use persistent
classes which require a lot of functions to be defined. This is done by
setting the macros "THIS" and "BASE", and some more, to the appropriate class
names and calling some macros within the class decleration afterwards.

e.g:
---------------------------------------------
#define THIS thisclass
#define BASE baseclass

class THIS : public BASE{

	SOME_MACRO_USING_THIS_AND_BASE;

}
---------------------------------------------

Please don't ask why we're not using macro parameters for this. There are
historical reasons (the package development started in 1989). 

This results in *many*  classes called "THIS" and in an unusable class
hierarchy. 

No my question: is it possible to give the parser a list of macro names which
are then substituted according to the definition within the files and not by
fixed value stored in a file? 

Thank you!

Best regards,
Chris Drexler

-- 
Dipl.-Inf. Christopher Drexler, Lehrst.f. Mustererkennung _    __  __ ___ 
Institut f. Informatik, Universitaet Erlangen-Nuernberg  | |  |  \/  | __|
WWW : http://www5.informatik.uni-erlangen.de/~drexler  	 | |__| |\/| | _| 
GPG : http://www.keyserver.net                           |____|_|  |_|___|

                 reply	other threads:[~2002-02-21 20:06 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=20020221210532.B14796@faui5pc48.informatik.uni-erlangen.de \
    --to=drexler@informatik.uni-erlangen.de \
    --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).