On Tue, 1 Mar 2005, Prof A Olowofoyeku (The African Chief) wrote: > Instead of starting a totally separate project, wouldn't it be better > to coordinate your efforts with the GPC development team?
Effective coordination will require, for a start, the GPC mailing list to accept messages from nonsubscribers. As is those who CC messages there just get bounces, so it's best not to try to CC them; anyone reading this discussion only on the GPC list will get a very partial view. If GPC developers are interested in having GPC integrated in GCC 4.1 and are willing to have it play by the same rules as the rest of GCC - note that the Ada maintainers made substantial changes to how they contributed patches to GCC in order to follow usual GCC practice more closely - then of course coordination would be desirable. If the GPC developers would prefer to continue to develop GPC independently of GCC, this need not stop integration of some version of GPC in GCC. I would hope in that case, however, there would still be better and closer cooperation between the two lines of development than there has been after the g95/gfortran fork (for example, that the GPC developers would be willing to make the version control repository used for actual development accessible to the public so individual patches can be extracted and merged as such). The GCC development processes are documented on <http://gcc.gnu.org/>. Some of the technical requirements on front ends are documented at <http://gcc.gnu.org/onlinedocs/gccint/Front-End.html> but that is just a checklist of pieces of a front end rather than full details of what is good practice (for example, the rules in the Make-lang.in file should be as similar as possible to those used for other languages where there is a common pattern used). -- Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ [EMAIL PROTECTED] (personal mail) [EMAIL PROTECTED] (CodeSourcery mail) [EMAIL PROTECTED] (Bugzilla assignments and CCs)
