Basile - > I'm quite tempted to start working on a rewrite of gengtype in C++ (using > C++03 standard). > > One of the reasons is that gengtype is really in bad shape, and nobody > understands it well. Another reason is that gengtype needs to be enhanced to > accept at least common C++ containers (like std::vector or std::map, or > probably a GCC specific variant of them whiwh would be notably > gcc_vector<typename ElemType,bool GGCed) and gcc_map<typename > Keytype,typename Elemtype,bool GGCed>)
> If I start working on that (very probably inside the MELT branch at first) > do I have a reasonable chance for that to be accepted in some trunk? Since no other GCC part is using C++ currently, I believe this would be rather poor first module choice to convert to C++. If C++ was already a non-optional requirement, then C++ conversion would be OK, but I believe this rewrite should be made in conjunction with current requirements and not in anticipation of some future requirement (or you risk rewriting it twice). -- Laurynas
