public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gcc 4.3.4 ---> 4.4.1
Date: Sat, 15 Aug 2009 19:17:33 +0200	[thread overview]
Message-ID: <200908151917.33788.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <5bdc1c8b0908150942y37996f4dtdf471a7456d64565@mail.gmail.com>

On Saturday 15 August 2009 18:42:11 Mark Knecht wrote:
> Alan,
>    I agree with your description, but I disagree that the upgrade
> guide is actually very clear about this. It has us upgrade the
> compiler (OK), switch to the new compiler (OK), rebuild the libtool
> stuff (OK) then then states:
>
> http://www.gentoo.org/doc/en/gcc-upgrading.xml
>
> <QUOTE>
> To be completely safe that your system is in a sane state, you must
> rebuild the toolchain and then world to make use of the new compiler.

And I disagree with you. The Gentoo docs are written in a style similar to 
RFCs, with very explicit meanings attached to words like SHOULD, MUST, MAY, 
CAN and others.

It is not the colloquial meaning, where these things pretty much all mean the 
same thing.

The document says "to be completely safe" - this does not mean that you will 
be unsafe it you don't do it, it simply means that it does in fact guarantee a 
form of safety if done. You cannot assume the negative must be true.

The later use of the word "must" does not apply to the general case (i.e. you 
must do it regardless), it depends on the prior "if" statement and should be 
read as "if you want to take advantage of this guarantee, do the following'

I do agree with you that the document should be reworded. Not because it's 
unclear, but because this topic comes up so often; and it almost always comes 
down to a lessened ability to read correct English - too many people have 
buggy language parses in their heads [I'm not accusing you of that :-) I'm 
speaking in general]

-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2009-08-15 17:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 23:17 [gentoo-user] Gcc 4.3.4 ---> 4.4.1 felix
2009-08-14 23:29 ` [gentoo-user] " walt
2009-08-15  0:33   ` felix
2009-08-15  0:43     ` Nikos Chantziaras
2009-08-15 16:48       ` Mark Knecht
2009-08-15 16:59         ` Nikos Chantziaras
2009-08-15 17:07       ` 7v5w7go9ub0o
2009-08-15 17:39         ` Nikos Chantziaras
2009-08-15 18:35           ` 7v5w7go9ub0o
2009-08-15 18:52             ` Nikos Chantziaras
2009-08-15 18:57               ` Nikos Chantziaras
2009-08-15 15:50     ` Alan McKinnon
2009-08-15 16:42       ` Mark Knecht
2009-08-15 16:49         ` Nikos Chantziaras
2009-08-15 17:10           ` Mark Knecht
2009-08-15 17:06         ` Dirk Heinrichs
2009-08-15 17:18           ` Mark Knecht
2009-08-15 17:28             ` Alan McKinnon
2009-08-15 17:24           ` Nikos Chantziaras
2009-08-15 17:37             ` Dirk Heinrichs
2009-08-15 17:40               ` Nikos Chantziaras
2009-08-16 12:43               ` Alan McKinnon
2009-08-15 17:25           ` Alan McKinnon
2009-08-15 17:39             ` Dirk Heinrichs
2009-08-15 17:17         ` Alan McKinnon [this message]
2009-08-15  7:22 ` [gentoo-user] " Neil Bothwick

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=200908151917.33788.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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