James A. Morrison wrote:
> I've decided I'm going to try to take the time and cleanup and update
> the Pascal frontend for gcc and try it get it integrated into the
> upstream source.
Nice to hear that you want to work on Pascal. However did you notice
that gpc _is_ changing. In particular, the latest snapshot is
gpc-20050217.tar.bz2 (it looks that you started from earlier version).
Since you plan to work on your own branch, it is wise to plan for
easy merge with frontend changes.
Joseph S. Myers wrote:
> 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.
I would like to see GPC integrated in GCC. However, I feel that playing
by the GCC rules I could do substantially less work for GPC that I am
doing now. GCC rules pay off when there is critical mass of developers.
My ipression was that GPC do not have that critical mass -- so it was
better to keep GPC outside of GCC. Jim contibution can change that.
> 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).
ATM GPC does not use version control. Frank Heckenbach just periodically
collects flowing patches and his changes into releases.
--
Waldek Hebisch
[EMAIL PROTECTED]
