public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/14385] New: Parse errors encountered where there shouldn't be
@ 2004-03-02 15:04 shayne dot fletcher at rbos dot com
  2004-03-02 15:10 ` [Bug c++/14385] " bangerth at dealii dot org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: shayne dot fletcher at rbos dot com @ 2004-03-02 15:04 UTC (permalink / raw)
  To: gcc-bugs

Parse error encountered. The following program demonstrates the problem:

struct date
{
  date(long l) {}
};

struct period
{
  period(const date& s, const date& e) {}
};

void f()
{
  long I = 0L, J = 0L, arr[1] = {0L};

  period p(date(I), date(J)); // succeeds
  period r(date(0L), date(J)); // succeeds
  period s(date(0L), date(0L)); // succeeds
  period t(date(arr[0]), date(arr[0])); // succeeds

  period q(date(I), date(0L)); // fails: parse error
  //period u(date(arr[0]), date(0L)); // fails: parse error
}

int main()
{
  return 0;
}

-- 
           Summary: Parse errors encountered where there shouldn't be
           Product: gcc
           Version: 3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: shayne dot fletcher at rbos dot com
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14385


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

* [Bug c++/14385] Parse errors encountered where there shouldn't be
  2004-03-02 15:04 [Bug c++/14385] New: Parse errors encountered where there shouldn't be shayne dot fletcher at rbos dot com
@ 2004-03-02 15:10 ` bangerth at dealii dot org
  2004-03-02 15:13 ` pinskia at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: bangerth at dealii dot org @ 2004-03-02 15:10 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From bangerth at dealii dot org  2004-03-02 15:10 -------
This is one of our most often reported bugs, see the bugs section 
of our web page. It is fixed in 3.4. 
 
W. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14385


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

* [Bug c++/14385] Parse errors encountered where there shouldn't be
  2004-03-02 15:04 [Bug c++/14385] New: Parse errors encountered where there shouldn't be shayne dot fletcher at rbos dot com
  2004-03-02 15:10 ` [Bug c++/14385] " bangerth at dealii dot org
@ 2004-03-02 15:13 ` pinskia at gcc dot gnu dot org
  2004-04-21  1:58 ` pinskia at gcc dot gnu dot org
  2004-04-21  2:04 ` pinskia at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-03-02 15:13 UTC (permalink / raw)
  To: gcc-bugs



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |3.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14385


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

* [Bug c++/14385] Parse errors encountered where there shouldn't be
  2004-03-02 15:04 [Bug c++/14385] New: Parse errors encountered where there shouldn't be shayne dot fletcher at rbos dot com
  2004-03-02 15:10 ` [Bug c++/14385] " bangerth at dealii dot org
  2004-03-02 15:13 ` pinskia at gcc dot gnu dot org
@ 2004-04-21  1:58 ` pinskia at gcc dot gnu dot org
  2004-04-21  2:04 ` pinskia at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-04-21  1:58 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-21 01:39 -------
Reopening as this is a dup of ...

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14385


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

* [Bug c++/14385] Parse errors encountered where there shouldn't be
  2004-03-02 15:04 [Bug c++/14385] New: Parse errors encountered where there shouldn't be shayne dot fletcher at rbos dot com
                   ` (2 preceding siblings ...)
  2004-04-21  1:58 ` pinskia at gcc dot gnu dot org
@ 2004-04-21  2:04 ` pinskia at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-04-21  2:04 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-21 01:40 -------
bug 11796.

*** This bug has been marked as a duplicate of 11796 ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14385


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

end of thread, other threads:[~2004-04-21  1:40 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-02 15:04 [Bug c++/14385] New: Parse errors encountered where there shouldn't be shayne dot fletcher at rbos dot com
2004-03-02 15:10 ` [Bug c++/14385] " bangerth at dealii dot org
2004-03-02 15:13 ` pinskia at gcc dot gnu dot org
2004-04-21  1:58 ` pinskia at gcc dot gnu dot org
2004-04-21  2:04 ` pinskia at gcc dot gnu dot org

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