What happened to libfeutil?

[Zack Weinberg]

"S. Bosscher" <S.Bosscher@student.tudelft.nl> writes:

>> There's now a libcpp and libcpp/include which may get the same
>> treatment, because Ben wants it called libpp. (I'd really appreciate
>> some opinions on what this directory *should* be called.  It is mostly
>> cpplib, but it's getting a number of pieces of common functionality
>> too, like line-map.c and hashtable.c.)
>
> Why hashtable/linemap?

Because all users of cpplib need these, whether or not they are front
ends.

> Does that mean that all front ends need to link with cpplib (to be
> able to use get_identifier), or will such files somehow be separate.
> I thought they were in libbackend now?

It is likely that "../libcpp/libcpp.a" will be on the link line for
all front ends, but you shouldn't take that to mean that any more of
cpplib is getting sucked in than is now - line-map.c and hashtable.c
remain isolated from the rest of the library.

I want to make cpplib more modular.  GDB wants the macro expander, but
doesn't need the lexer nor the directive processor; Java could
probably use the lexer, but doesn't want anything else; any front end
could make use of the input-file stack and the character conversion
logic; etc etc.

This is why I was thinking of calling the directory libfeutil - to
suggest that this wasn't just a preprocessor, but a generic utility
library for source-code grinders.  I changed my mind because I decided
that in the present state, i.e. >80% preprocessor, it would just be
confusing.

zw