Peter Gerwinski peter@gerwinski.de writes:
I am thinking about doing a major change in the structure of the GPC source.
Until now, some GPC source files (gpc-typeck.c, gpc-common.c, ...) are modified GCC source files, and all GPC-specific changes are marked `#ifdef GPC'.
AFAIK, the reason for this is that we want to profit with GPC from bug fixes in the GCC frontend.
But are we really doing this ?
Meanwhile the `#ifdef GPC' parts are getting more and more making the files in question less and less readable. Furthermore, sticking to the GCC frontend prevents me from changing the parameter lists of certain central functions, thus introducing code duplication and unncessary bugs.
What do you think?
I think it is a good idea. I had been considering starting the effort on this myself. It should make the front end simpler.
Nick.
Hello, this is my first post to this list. I am running Mklinux with egcs-1.1.1. Is anyone working on a port? I didn't see anything at the gpc website, so I guess my best alternative is CW! I had a hard time finding this list, but I'm glad I've finally found it...
Taro Fukunaga tarozax@earthlink.net
Taro Fukunaga wrote:
Hello, this is my first post to this list. I am running Mklinux with egcs-1.1.1. Is anyone working on a port?
GPC version gpc-19990118 works well with egcs-1.1.1. Just get the sources from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ , install and enjoy.
I didn't see anything at the gpc website, so I guess my best alternative is CW!
CW?
I had a hard time finding this list, but I'm glad I've finally found it...
It's mentioned on our web site and in every README or other official statement we give out.
Hope this helps,
Peter