Hi,
Stefan very reasonably wrote about first agreeing on goals. So my goal is:
===============================================
To have open-source refactoring tool for C++.
===============================================
And my vision on how to get there is:
==================================
First focus on OpenC++ Core Lib.
==================================
OpenC++ includes several modules having different complexity and
different reuse potential. For example driver calling compilers and
linkers is quite complex but its reuse potential is low. IMO the most
important modules of OpenC++ are lexer, parser, program object model and
static analyzer, and we should focus on them.
I suggest to
(1) Take these modules out and call them "OpenC++ Core Lib",
(2) Focus on Core Lib only, forgetting about compatibility
with the rest of OpenC++ for some time,
(3) Implement templates and overloading in Core Lib,
along with appropriate unit tests, document it honestly,
(4) Go back to the rest of OpenC++ and reimplement it using
Core Lib API; this will be the proof of concept that the API
is complete
How to do this:
(1) Have one repository.
Let's put the code base of OpenC++ Core Lib in one repo and work
in it. Let it be hosted on SF or on fresco or wherever,
but let's have ONE repo for OpenC++ Core Lib. Present situation
with Gilles here and Stefan there only brings confusion
and problems with merging.
(2) Minimize impact of trouble-makers.
Majority of my time invested in 2.8 release went into
solving problems related to libgc, libltdl, libtool,
autoconf/automake (in this order).
I suggest to minimize impact of these technologies
on OpenC++ Core Lib, so that we can focus on templates
and overloading, and not on dynamic linking.
(3) Keep OpenC++ Core Lib easy to compile and test.
Several potential volunteers approached OpenC++ in during the last
year, but were distracted by problems with compiling on WinXP.
This shrinks the pool of potential volunteers.
Please let me know what you think. If you guys find this agenda in
common with your goals, then let's try to get down to more technical
terms and maybe some timelines or schedule.
BR
Grzegorz
|
