Path: utzoo!telly!ddsw1!lll-winken!uunet!tut.cis.ohio-state.edu!BOURBAKI.MIT.EDU!ghoti
From: ghoti@BOURBAKI.MIT.EDU
Newsgroups: gnu.gcc.bug
Subject: (none)
Message-ID: <8809250158.AA13018@hypatia.mit.edu>
Date: 25 Sep 88 01:58:55 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 11

One of the things that makes gcc harder to debug is that so many important
routines are implemented as macros. For example, this is the case for many
of the obstack routines. When one calls one of them in GDB, the debugger
doesn't know how. Is there any reason why they were implemented in this
way instead of writing them out in full as routines with full code ?
Similar problems exist for routines in obstack.c which have the same names
as macros in obstack.h and which are protected from having their names
expanded by the preprocessor by putting them in parnetheses. Again, one
can't chase them down and the style, in any case, seems kind of kludgy.

Allan Adler
ghoti@cauchy.mit.edu