Adriaan van Os wrote:
Gerrit P. Haase wrote:
I don't speak of releases or snapshots and how to distrbute these, I'm talking of services for developers (mailinglists, bugtracking sytem, feature request system, source repository), all these things are needed if you need to manage more than ten developers.
So - where are these ten developers, working daily on the gpc source code ? This is hypothetical. You are talking about the wrong problem,
I don't include GPC with the Cygwin GCC distribution currently because: - no according MinGW version available because GPC is no regular part of the GCC. - too much work to do, everytime I do a release it is difficult enough to get it out anyway, no time to integrate another backend. - GPC with 3.4.x seems to be broken or at least not supported.
I don't report bugs because I don't build GPC on a regular basis and so I count not as a developer / tester / user, whatever you want. But you would count me if I were building GPC on a regular basis and if I would be reporting errors / bugs / problems when building / using it or running the testsuite.
Since it is too much hassle to integrate an extern frontend into GCC or it is entirely impossible since the needed MinGW port is not available you have lost me as developer / tester / user.
I have done this before and there is still a GCC with Pascal frontend part of the Cygwin GCC distribution, however I don't see that it will happen with 3.4.x.
Gerrit