Merge cpplib and front end hashtables, part 1

[Daniel Berlin]

Stan Shebs <shebs@apple.com> writes:

> Daniel Berlin wrote:
> > 
> > Since I couldn't get CPPLIB integrated quickly, I just made it do
> > simple macro expansion.
> 
> Not to dis your work (and I still would like to see the code!...),

Well, if we can resolve how to get the macros into cpplib without me
having to write 300 lines of code to walk the symbol tables, and
insert them, and have to execute this code every time we process an
input line, i'd be done and send you the code.

> but sooner or later we'll have to use the full cpplib functionality.
> The gold standard for GDB expression evaluation is that it pass the
> "cut-n-paste" test, where you can take any fragment of source code,
> and if GDB can get a valid expression out of it, it will evaluate
> the expression correctly.  For now, until somebody has time to pull
> cpplib into GDB, it suffices to have both GCC and GDB people aware
> of the goal, and to account for the possibility when doing other
> hacking activities.  (Just the mechanics of using cpplib in GDB will
> be interesting - we will probably need cpplib to be a sibling of
> libiberty for instance).
> 
> Stan

-- 
"I took a baby shower.
"-Steven Wright