Command-line options and CFG file (was: New Alpha)

Wed, 2 Apr 1997 20:11:12 +0200 (MET DST)

According to The African Chief:
> [...] In case you haven't done this, can you
> introduce a .CFG file (like with Borland) where one can
> put all the command line switches that they want to use?

I have an old version of GCC for some special hardware here (without
source #@*!) which accepts a `@filename' option pointing to a file with
additional options.  We could, for example, do the same and make

    gpc @gpc.cfg

read a file `gpc.cfg' in the current directory. 

> The compiler will read the .CFG file before doing anything
> else, and will adjust its behaviour accordingly. I personally
> prefer this approach to using environment variables or the
> such.

So do I.

> You can make many sample .CFG files 
> (e.g., borland.cfg, extended.cfg, iso.cfg, etc) which people
> can then rename to GPC.CFG or whatever.

In principle this is not necessary:  By default, GPC understands all of
these dialects (as far as implemented) and you can specify one (or more)
of `--standard-pascal', `--extended-pascal', `--borland-pascal' to
restrict GPC's language to the specified dialects.

    Peter

  Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer
peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201]
 maintainer GNU Pascal [970401] - http://home.pages.de/~gnu-pascal/ [970125]

Peter Gerwinski (peter@agnes.dida.physik.uni-essen.de)