Re: [help-gengetopt] option name collision wi th builtin 'include' special directive

> however, I'm a bit reluctant about the command line option to disable,=
=20
> since gengetopt is having quite a lot of them ;)

[off] some day you must really take a look at our command line jungle :)=
) (59)

[on] However, I admit your concerns. I think that "include" is the most =
nature name you could come up with. Unfortunately others came up with th=
e same name for something completely different.

By the way, there is a theoretical problem with escaping. If an applicat=
ion is not prepared for that syntax, it might fail. I mean chances, prob=
ably fail probably not. It is certainly decreased by escaping because th=
e syntax which may collide would be more complex, but the probability ne=
ver will be 0 (zero).

However, sticking to escaping we could use C style inclusion if it does =
not hurt too much:=20
"include <file>" or something like that. I don't know how many people us=
e this feature of gengetopt.