public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Matthew Woehlke <mw_triad@users.sourceforge.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Doc is misleading
Date: Wed, 23 May 2007 16:04:00 -0000	[thread overview]
Message-ID: <m3646jlejc.fsf@localhost.localdomain> (raw)
In-Reply-To: <f1vqi6$l9c$1@sea.gmane.org>

Matthew Woehlke <mw_triad@users.sourceforge.net> writes:

> I don't care if it gives a 500 page dissertation on the meaning of
> life. :-) 'info gcc' says this:
> 
> <quote>
>   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.
> </quote>
> 
> ...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

  reply	other threads:[~2007-05-23 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 11:00 Simple linking problem gccNewbie
2007-05-10 11:07 ` Andrew Haley
2007-05-10 11:38   ` gccNewbie
2007-05-10 11:40     ` John (Eljay) Love-Jensen
2007-05-10 11:42     ` Andrew Haley
2007-05-10 16:00     ` Matthew Woehlke
2007-05-10 18:18       ` gccNewbie
2007-05-10 18:27         ` Doc is misleading (was: Simple linking problem) Matthew Woehlke
2007-05-10 18:36           ` Doc is misleading David Daney
2007-05-10 19:08             ` Matthew Woehlke
2007-05-23 16:04               ` Ian Lance Taylor [this message]
2007-05-23 21:45                 ` Matthew Woehlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3646jlejc.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=mw_triad@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).