From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by sourceware.org (Postfix) with ESMTPS id A1FDB385AC1E for ; Mon, 21 Mar 2022 10:21:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A1FDB385AC1E Received: by mail-wm1-x32e.google.com with SMTP id bi13-20020a05600c3d8d00b0038c2c33d8f3so7373573wmb.4 for ; Mon, 21 Mar 2022 03:21:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=O4VGHgIPVIEGU+hq2x5z3+7Dtzmllsi7e4DSs1VGL4g=; b=JhEq3/45m+GbXw6SGRefwQqLS3CpnPT5f73pIOyJlCTiE5oj9dGvIIBVisQ8rcn/2i 7ppzBk+nSfjqVwk+2UhifO0P2rIXw13g9poj0SSwgo5AJtyKNoEKR6guWrNefATiBp5q 5j9ZhwypSmrGHbZDVS89CzuY/AoenoFKkDLayEcY/2hxuz1NmOt+LsvKSJaweOZRHs6k mfQrD2dHzTpTUmrkWbUXZEzJbuezmJdHQg5fwD44pzAvef9UhGENvzqOTSST2JC7IwVF J92q1zIeZi7HRt9GtEnrigB5DbMi9br12k/Vi/ZDgLHkFPAMov2AA93gUQLbKQGXOaRm q2VQ== X-Gm-Message-State: AOAM530VJP7ovY4PA8LIr83LPwn1x7IA1wFe74bFjl30MXXtHxQIpPy2 2sPGAPYhvdwCYaB4p5S8zBvKVfsgqhQBmlvrpyOWyVvu X-Google-Smtp-Source: ABdhPJw0Kwa5765fL3AiXMHbKeWQk4Mbf4wTWnEe0MIEF6KYoJMIuk/WXpABdTvyfhkHF6zzPAdQmnDOpDx8ecZsP00= X-Received: by 2002:a05:600c:3547:b0:38c:92a6:5a17 with SMTP id i7-20020a05600c354700b0038c92a65a17mr10281564wmq.20.1647858116478; Mon, 21 Mar 2022 03:21:56 -0700 (PDT) MIME-Version: 1.0 References: <20220316143409.24cb3e7fd17c6b73acaee586@schemamania.org> <20220317122136.d15c4fd4f6ea9fec2cbc0938@schemamania.org> <20220319131029.49490fb71bf0bbaae4c598bf@schemamania.org> In-Reply-To: <20220319131029.49490fb71bf0bbaae4c598bf@schemamania.org> From: Jonathan Wakely Date: Mon, 21 Mar 2022 10:21:45 +0000 Message-ID: Subject: Re: passing command-line arguments, still To: "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2022 10:22:04 -0000 On Sat, 19 Mar 2022 at 17:10, James K. Lowden wrote: > > > 3. The "f" stands for "flag", meaning on/off. > > > > It does stand for "flag", and it looks like at some point in ancient > > history if was on/off, but then came options like -falign-loops=N. > > IME, someone made a mistake in the past, and that mistake is now > becoming mistaken for a standard. I don't mind living with some cruft > -- it's not as though gcc is unique in that regard -- but at the same > time I see no reason to vernerate it or perpetuate it. > > In plain words, if we recognize that -f indicates an on/off switch, > let's use it that way, deprecate those that don't, and not add new -f > options that take arguments. Why should the historical convention that hasn't been true for years win over the current one that is in wide usage? Trying to revert to some idealised point in history will just cause pain and break things now. It's better to just accept that the original meaning mutated and "on/off flag" is no longer true.