Prof A Olowofoyeku (The African Chief) wrote:
On 26 May 2004 at 1:18, Frank Heckenbach wrote:
[...]
If we don't find anything suitable (say, <= 3 letters and making sense), I suggest to rename the gpc executable to something longer and call gp gpc. This will, of course, require some incompatible changes, but I'd rather have the future recommended way of using GPC to have the more "comfortable" and easy to use name while the "old style" and C compatible plain interface (which will probably mostly occur in legacy Makefiles then) can have a longer name (probably starting with `gpc').
How about "gpm"
That's the name of a well-known program (console mouse driver).
or "gpi" or "gpd"
These are the file name suffixes used by GPC and GP. If the name was different, we could use that name as the suffix for configuration files. (I don't like `.cfg' as you suggested. First, it's very generic; second, using program specific config files, if `foo.pas' is a program, then `foo.cfg' might be used by the programmer for a program config file, so we shouldn't use that name as the program build config file. I.e., if the tool is called GP, I'd have used `foo.gp' as the config file name. But `foo.gpi' and `foo.gpd' are already used. Of course, we could think about renaming one of them as well -- preferably gpd because it isn't so widespread yet.)
or "cgp"?
Hmm, doesn't seem to be taken, at least in Debian ...
Frank