On 18 Jul 00, at 16:14, Peter Gerwinski wrote:
[...]
GPC's current behaviour is due to consistency with other GNU compilers and with Borland Pascal where you also have to give an option `/M' in order to get the effect of `--automake'.
The difference is that compiling a program that uses units with BP normally works even if you don't specify '/M', unless you have changed the interface of a used unit and the compiler cannot find the new things in the pre-compiled TPUs. With GPC on the other hand, my experience is that '--automake' is normally needed even when there are precompiled units and the interfaces have not changed. Thus, having the automake feature turned on by default seems quite sensible (and I am not sure why one would want to turn it off, except to use '--autobuild').
However if we agree on this list that `--automake' should be the default, I wouldn't mind changing GPC that way.
I vote for this.
Another solution: It is planned to distribute an external utility in the future which does the same as `--automake' and more. This will make GPC's internal `--automake' facility obsolete.
What do you think?
The utility is fine, but I think that just being able to type 'gpc foo.pas' is a good thing, even when 'foo.pas' uses other units.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro v5.22.1 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief@bigfoot.com