From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27060 invoked by alias); 10 Mar 2002 19:36:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 27036 invoked by uid 71); 10 Mar 2002 19:36:00 -0000 Date: Sun, 10 Mar 2002 11:36:00 -0000 Message-ID: <20020310193600.27035.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Florian Weimer Subject: Re: ada/5907: The Ada front end lacks a proper manual Reply-To: Florian Weimer X-SW-Source: 2002-03/txt/msg00324.txt.bz2 List-Id: The following reply was made to PR ada/5907; it has been noted by GNATS. From: Florian Weimer To: "Joseph S. Myers" Cc: , , Subject: Re: ada/5907: The Ada front end lacks a proper manual Date: Sun, 10 Mar 2002 20:28:59 +0100 "Joseph S. Myers" writes: > On Sun, 10 Mar 2002, Florian Weimer wrote: > >> We would need a couple of hundered macros, I think. For example, the >> preprocessing rewrites all strings like "hello.adb" to "HELLO.ADB", >> "hello.o" to "HELLO.OBJ", and so on. If you had to write >> "@helloadb{}" and "@helloo{}", reading the sources would become rather >> difficult. > > Define a macro that's used like @vmsfile{hello.adb}{HELLO.ADB}. This still reduces readability to a certain extent. In addition, there are about 100 command names and options which have to be replaced in the VMS version. Of course, you could use the macro approach for this one, too, but we decided not to do that. Anyway, when I've finished writing the preprocessor, I can tweak it so that it writes a macroized Texinfo version, and we can still decide if we want to use this one, or the keep the preprocessor.