public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pcarlini@unitus.it
To: gcc-gnats@gcc.gnu.org
Cc: nbecker@fred.net
Subject: c++/5577: Parse error (both mainline and newparser)
Date: Fri, 01 Feb 2002 16:26:00 -0000	[thread overview]
Message-ID: <20020202002123.31116.qmail@sources.redhat.com> (raw)


>Number:         5577
>Category:       c++
>Synopsis:       Parse error (both mainline and newparser)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 01 16:26:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Paolo Carlini / Neal D. Becker
>Release:        3.1 20020201 &  current newparser branch
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
The following code snippet triggers a parse error @line 26:
////////
template<typename coeftype>
struct IIR {
  IIR () {}
  template <class outputtype>
  outputtype Compute (coeftype x) {
    return outputtype();
  }
};

// This is Ok.
IIR<double> iir;
double out_iir = iir.Compute<double>(0.0);

// This is Ok.
struct JTC_fading2 {
  void Iterate () {
    double out_iir = iir.Compute<double>(0.0);
  }
  IIR<double> iir;
};

// This is NOT Ok.
template<typename rng_t>
struct JTC_fading {
  void Iterate () {
    double out_iir = iir.Compute<double>(0.0); // <- Error
  }
  IIR<double> iir;
};
//////////
>How-To-Repeat:
EDG-based C++ compiler have no problem with it.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-02-02  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 16:26 pcarlini [this message]
2002-02-01 16:42 paolo

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=20020202002123.31116.qmail@sources.redhat.com \
    --to=pcarlini@unitus.it \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=nbecker@fred.net \
    /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).