public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7016 Date: Thu, 23 Jan 2003 17:06:00 -0000 [thread overview] Message-ID: <20030123170601.12734.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7016; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/7016 Date: Thu, 23 Jan 2003 10:59:49 -0600 (CST) > Hmm, of course you could deprecate this. In any case, I came to note > this because such code compiled file with 2.95.3. Which code? The code in the example passed the 2.95 compiler for me, but created errors in the assembler since the operator was mangled as "<invalid operator>" (sic). > Whether or not the > assignment versions make a lot of sense is another question - I consider > them as usefule (or useless) as the other assignment operators which I'm > sure you won't put under question. Sure not. I suggested deprecating <? and >?, and if they are, then the assignment versions should be as well. However, I see that I misunderstood their meaning. I was reading them as <=? instead of <?=, i.e. "give the element that is smaller or equal to the other one", instead of "assign the smaller one of the two". The former doesn't make sense, since it is equivalent to the <? operator. Sorry, my bad. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-01-23 17:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-23 17:06 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-23 16:46 c++/7016 Wolfgang Bangerth 2003-01-23 15:46 c++/7016 Wolfgang Bangerth 2003-01-23 15:46 c++/7016 Wolfgang Bangerth 2003-01-23 15:46 c++/7016 Wolfgang Bangerth
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=20030123170601.12734.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).