public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: jwakely.gcc@gmail.com (Jonathan Wakely)
Cc: ptb@inv.it.uc3m.es (Peter Breuer),
	david@westcontrol.com (David Brown),
	       lh_mouse@126.com (lh_mouse),
	gcc-help@gcc.gnu.org (gcc-help)
Subject: Re: signed/unsigned integer conversion for right shift seems
Date: Wed, 07 Feb 2018 17:25:00 -0000	[thread overview]
Message-ID: <201802071725.w17HPBlE003682@nbd.it.uc3m.es> (raw)
In-Reply-To: <CAH6eHdSwGfMhQYpYr3Cqv-jSeQDEKRxTPr6euTaCE8odbKhysQ@mail.gmail.com> from "Jonathan Wakely" at Feb 07, 2018 04:39:21 PM

"Also sprach Jonathan Wakely:"
> 
> On 7 February 2018 at 16:34, Peter T. Breuer wrote:
> > I'll repeat the paragraph from my summary this morning.
> 
> Please don't, your sophistry is still off-topic. Repeating it doesn't

Kindly explain why explaining is off-topic in your opinion.

> make it any less so.

 Sophistry \Soph"ist*ry\, n. [OE. sophistrie, OF. sophisterie.]
 The art or process of reasoning; logic. [Obs.] [1913 Webster]

Correct. I am exact, which is the minimum anyone can be.

> The insight you finally gave me credit for wasn't even mine

It is.  Kindly point to somebody who says it before you?  For example, I
see from you Tue 16.45:

  You've already been told that 6.5.7 says "The integer promotions are
  performed on each of the operands. " and says nothing about
  conversions.

which is not it. Either you still don't get what IT is, or ... I don't
know. To give you the clue, here is my response (my caps) at 20.11:

  I see nothing that says that conversions should NOT be applied to
  their operators.

Got it yet? Here is where you did give the clue. I'll help again with
caps:

  > What, specifically, do you see in 6.5.7 that allows the
  > conversion specified by the general rule of conversions
  >
  >  If one operand has an unsigned type T whose conversion rank is
  >  at least as high as that of the other operand's type, then the other
  >  operand is converted to type T.
  >
  > NOT to be applied?  
  > 
  > BECAUSE it doesn't say they are applied. As I pointed out in  

Get it? You finally exposed your REASONING, for the very first and only
time.

That single instance of displayed reasoning was enough for me.

You could have saved yourself you had merely gone to that ordinary
length beforehand, but no.

> originally, but as I'd also said in an earlier mail, you aren't paying
> attention. Too busy stroking yourself for being so clever.

I am not clever! Just ordinary! 

> Now please go away, you tedious fart.

Pot.


PTB

  reply	other threads:[~2018-02-07 17:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 15:03 signed/unsigned integer conversion for right shift seems against C99 rule Peter Breuer
2018-02-06 15:21 ` Tadeus Prastowo
2018-02-06 15:29   ` signed/unsigned integer conversion for right shift seems against Peter T. Breuer
2018-02-06 15:38     ` Tadeus Prastowo
2018-02-06 16:17       ` Peter T. Breuer
2018-02-06 15:22 ` signed/unsigned integer conversion for right shift seems against C99 rule Alexander Monakov
2018-02-06 15:22 ` Liu Hao
2018-02-06 15:31   ` David Brown
2018-02-06 15:50   ` signed/unsigned integer conversion for right shift seems Peter T. Breuer
2018-02-06 15:57     ` Jonathan Wakely
2018-02-06 16:42       ` Peter T. Breuer
2018-02-06 16:45         ` Jonathan Wakely
2018-02-06 17:19           ` Peter T. Breuer
2018-02-06 17:35             ` Jonathan Wakely
2018-02-06 18:23               ` Peter T. Breuer
2018-02-06 18:27                 ` Jonathan Wakely
2018-02-06 18:37                   ` Tadeus Prastowo
2018-02-06 18:47                     ` Jonathan Wakely
2018-02-06 19:43                       ` Peter T. Breuer
2018-02-06 20:08                         ` Tadeus Prastowo
2018-02-06 20:15                           ` Jonathan Wakely
2018-02-07  9:59                             ` Peter T. Breuer
2018-02-07 12:28                               ` David Brown
     [not found]                                 ` <201802071634.w17GYiEL000904@nbd.it.uc3m.es>
2018-02-07 16:39                                   ` Jonathan Wakely
2018-02-07 17:25                                     ` Peter T. Breuer [this message]
2018-02-07 17:39                                       ` Jonathan Wakely
2018-02-07 18:32                                         ` Peter T. Breuer
2018-02-07 18:41                                           ` Jonathan Wakely
2018-02-07 17:39                                       ` Tadeus Prastowo
2018-02-07 18:50                                         ` Peter T. Breuer
2018-02-07 18:11                                       ` Jonathan Wakely
2018-02-06 19:28                   ` Peter T. Breuer
2018-02-06 20:11                     ` Jonathan Wakely
2018-02-06 23:49                       ` Peter T. Breuer
2018-02-07  2:04                         ` Vincent Lefevre
2018-02-07  9:30                           ` Peter T. Breuer
2018-02-06 21:18                 ` Chris Hall
2018-02-06 17:44             ` Tadeus Prastowo
2018-02-06 19:00               ` Peter T. Breuer

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=201802071725.w17HPBlE003682@nbd.it.uc3m.es \
    --to=ptb@inv.it.uc3m.es \
    --cc=david@westcontrol.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=lh_mouse@126.com \
    /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).