public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/7016: missing definitions for <?= and >?=
@ 2002-06-14 14:46 lerdsuwa
  0 siblings, 0 replies; 4+ messages in thread
From: lerdsuwa @ 2002-06-14 14:46 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, jbeulich, nobody

Synopsis: missing definitions for <?= and >?=

State-Changed-From-To: open->feedback
State-Changed-By: lerdsuwa
State-Changed-When: Fri Jun 14 09:59:07 2002
State-Changed-Why:
    Please provide a preprocessed source as described at
      http://gcc.gnu.org/bugs.html

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7016


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: c++/7016: missing definitions for <?= and >?=
@ 2003-01-23  3:11 bangerth
  0 siblings, 0 replies; 4+ messages in thread
From: bangerth @ 2003-01-23  3:11 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, jbeulich, nobody

Synopsis: missing definitions for <?= and >?=

State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Thu Jan 23 03:11:18 2003
State-Changed-Why:
    This is probably a corner case whether I should close the
    report: this has never worked (used to ICE)
    ---------------------------------
    class C {};
    C operator <?= (C) { return C(); }
    --------------------------------------
    I don't think it was ever documented that one should be
    able to overload this operator (a gcc extension anyway).
    Now we at least get a reasonable error:
    g/a> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc:2: error: expected identifier
    x.cc:2: error: expected type-name
    x.cc:2: error: expected `,' or `;'
    
    So the fact that the new parser rejects the code is ok, and
    is not removing a documented extension.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7016


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: c++/7016: missing definitions for <?= and >?=
@ 2002-06-24  9:04 lerdsuwa
  0 siblings, 0 replies; 4+ messages in thread
From: lerdsuwa @ 2002-06-24  9:04 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, jbeulich, nobody

Synopsis: missing definitions for <?= and >?=

State-Changed-From-To: feedback->analyzed
State-Changed-By: lerdsuwa
State-Changed-When: Mon Jun 24 08:21:01 2002
State-Changed-Why:
    Test case added.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7016


^ permalink raw reply	[flat|nested] 4+ messages in thread

* c++/7016: missing definitions for <?= and >?=
@ 2002-06-13  4:16 jbeulich
  0 siblings, 0 replies; 4+ messages in thread
From: jbeulich @ 2002-06-13  4:16 UTC (permalink / raw)
  To: gcc-gnats


>Number:         7016
>Category:       c++
>Synopsis:       missing definitions for <?= and >?=
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 13 04:15:59 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Jan Beulich
>Release:        3.1
>Organization:
>Environment:
Cross compilers running on Cygwin (Win2K).
>Description:
This prevents code compiling with g++ 2.x to compile, and
since the preprocessor/tokenizer knows these tokens this
leads to ICEs.
>How-To-Repeat:
Compile and C++ source program containing either operator.
>Fix:
Add the two missing lines to operators.def.
>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-01-23  3:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-06-14 14:46 c++/7016: missing definitions for <?= and >?= lerdsuwa
  -- strict thread matches above, loose matches on Subject: below --
2003-01-23  3:11 bangerth
2002-06-24  9:04 lerdsuwa
2002-06-13  4:16 jbeulich

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).