On 15 Oct 2001, at 1:50, Frank Heckenbach wrote:
The specs file is system-wide and therefore should not change the default behaviour of the compiler. A private (per-user) script/alias that sets the options is the better way to go.
I would argue that the "better way to go" depends on the situation.
If I want to deploy GPC as an EP compiler only for a team, then setting up multiple per-user script files, and ensuring that each person actually uses their script file every time, would seem to be awkward and error-prone. The same argument would apply to any other team-wide settings (e.g., -fno- macros, or -funit-path).
Changing the default behavior of the compiler in these cases would be far safer and make far more sense than would attempting to force every user to invoke the compiler only by using the proper script.
Of course, per-user scripts make sense for individuals to set personal preferences.
-- Dave