This is the mail archive of the
mailing list for the GCC project.
Re: Can You Put Comments Into GCC Compiler Options Files?
- From: Ian Lance Taylor <iant at google dot com>
- To: Basile Starynkevitch <basile at starynkevitch dot net>
- Cc: "Craig Dedo" <craig at ctdedo dot com>, <gcc at gcc dot gnu dot org>
- Date: Wed, 23 Feb 2011 04:33:06 -0800
- Subject: Re: Can You Put Comments Into GCC Compiler Options Files?
- References: <!&!AAAAAAAAAAAYAAAAAAAAADwWT6ZWSIFJsr5qVFz+64/CgAAAEAAAAO1WTmtReHFMjzdDEp79oKUBAAAAAAfirstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
Basile Starynkevitch <email@example.com> writes:
> On Tue, 22 Feb 2011 18:09:40 -0800
> Ian Lance Taylor <firstname.lastname@example.org> wrote:
>> No comments are permitted in the contents of options files read using
>> the @file syntax. The contents of the file are simply interpreted as
>> command line arguments separated by whitespace. Double quotes, single
>> quotes, and backslashes may be used in the usual way to add whitespace
>> to arguments.
> Maybe we should change that. Do people find such a change useful for 4.7?
> If yes, with what comment lexical syntax? A leading # on a line?
I believe lThese option files were adapted from Windows, and they are
primarily for use on Windows, which has much stricter limits on command
line length than most Unix systems. We should implement whatever