public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jens.Maurer@gmx.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/1936: pseudo-construction and >> operator
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20010211215911.11376.qmail@sourceware.cygnus.com> (raw)

>Number:         1936
>Category:       c++
>Synopsis:       pseudo-construction and >> operator
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 11 14:06:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jens.Maurer@gmx.net
>Release:        gcc version 2.97 20010208 (experimental)
>Organization:
>Environment:
Linux menuett 2.2.13 #1 Mon Nov 8 15:51:29 CET 1999 i686 unknown
glibc 2.2.1
>Description:
The code below is legal, but rejected by gcc.

constant_shift_operator.cc:2: parse error before `>>' token
>How-To-Repeat:

int i = (int()) >> 5;

>Fix:
As a workaround, use int(0) instead of int()
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  0:00 Jens.Maurer [this message]
2002-11-20 19:01 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=20010211215911.11376.qmail@sourceware.cygnus.com \
    --to=jens.maurer@gmx.net \
    --cc=gcc-gnats@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: 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).