From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24579 invoked by alias); 21 Feb 2002 20:06:16 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 24491 invoked from network); 21 Feb 2002 20:06:14 -0000 Received: from unknown (HELO faui50.informatik.uni-erlangen.de) (131.188.35.50) by sources.redhat.com with SMTP; 21 Feb 2002 20:06:14 -0000 Received: from faui5pc48.informatik.uni-erlangen.de (faui5pc48.informatik.uni-erlangen.de [131.188.35.226]) by faui50.informatik.uni-erlangen.de (8.8.8/8.1.21-FAU) with ESMTP id VAA19017 for ; Thu, 21 Feb 2002 21:05:32 +0100 (MET) Received: (from drexler@localhost) by faui5pc48.informatik.uni-erlangen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) id g1LK5Wi14911 for sourcenav@sources.redhat.com; Thu, 21 Feb 2002 21:05:32 +0100 Date: Thu, 21 Feb 2002 13:59:00 -0000 From: Christopher Drexler To: sourcenav@sources.redhat.com Subject: replacing "defines" Message-ID: <20020221210532.B14796@faui5pc48.informatik.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-SW-Source: 2002-q1/txt/msg00096.txt.bz2 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 |____|_| |_|___|