From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14635 invoked by alias); 23 May 2007 15:57:35 -0000 Received: (qmail 14593 invoked by uid 22791); 23 May 2007 15:57:23 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 May 2007 15:57:21 +0000 Received: from zps38.corp.google.com (zps38.corp.google.com [172.25.146.38]) by smtp-out.google.com with ESMTP id l4NFv1sJ010557; Wed, 23 May 2007 08:57:01 -0700 Received: from localhost.localdomain.google.com (dhcp-172-18-119-189.corp.google.com [172.18.119.189]) (authenticated bits=0) by zps38.corp.google.com with ESMTP id l4NFuq0f017300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 23 May 2007 08:56:52 -0700 To: Matthew Woehlke Cc: gcc-help@gcc.gnu.org Subject: Re: Doc is misleading References: <10410954.post@talk.nabble.com> <17986.64743.402588.180994@zebedee.pink> <10411665.post@talk.nabble.com> <10418803.post@talk.nabble.com> <46436639.6060002@avtrex.com> From: Ian Lance Taylor Date: Wed, 23 May 2007 16:04:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-05/txt/msg00225.txt.bz2 Matthew Woehlke writes: > I don't care if it gives a 500 page dissertation on the meaning of > life. :-) 'info gcc' says this: > > > You can mix options and other arguments. For the most part, the order > you use doesn't matter. Order does matter when you use several options > of the same kind; for example, if you specify `-L' more than once, the > directories are searched in the order specified. > > > ...which IMO is misleading and should be fixed. While it might be nice > if we did, I don't think it is critical that we explain things here in > depth, as long as we /avoid/ giving the impression that no explanation > is needed, and that things work a particular way /which is wrong/. Two > or three sentences would be a great convenience, but even just /one/ > could save a lot of headaches. Thanks for the suggestion. I just committed this patch to help avoid this problem in future releases. http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01558.html Ian