public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jkanze@caicheuvreuse.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10255: error with functional object used in parentheses
Date: Fri, 28 Mar 2003 18:36:00 -0000	[thread overview]
Message-ID: <20030328172433.7684.qmail@sources.redhat.com> (raw)


>Number:         10255
>Category:       c++
>Synopsis:       error with functional object used in parentheses
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 28 17:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     James Kanze
>Release:        g++3 (GCC) 3.2.2
>Organization:
>Environment:
SunOS padev054 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10
>Description:
Following program fails to compile:

----------------less.cc----------------------
struct myless
{
    bool                operator()( char const* a, char const* b )
    {
        return a < b ;
    }
} ;

bool
f( char const* p, char const* p1, char const* p2 )
{
    return ( myless()( p1, p2 ) ) ;
}
----------------less.cc----------------------
compilation log:
---------------------------------------------
054@~/tmp/gcc3 (51): g++3 --verbose -c less.cc
Reading specs from /home/team02/jakan/gnu/lib/gcc-lib/sparc-sun-solaris2.8/3.2.2/specs
Configured with: ../gcc-3.2.2/configure --prefix=/home/team02/jakan/gnu --program-suffix=3 --enable-threads=posix
Thread model: posix
gcc version 3.2.2
 /home/team02/jakan/gnu/lib/gcc-lib/sparc-sun-solaris2.8/3.2.2/cc1plus -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=2 -D__GXX_ABI_VERSION=102 -Dsparc -Dsun -Dunix -D__svr4__ -D__SVR4 -D__PRAGMA_REDEFINE_EXTNAME -D__sparc__ -D__sun__ -D__unix__ -D__svr4__ -D__SVR4 -D__PRAGMA_REDEFINE_EXTNAME -D__sparc -D__sun -D__unix -Asystem=unix -Asystem=svr4 -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_XOPEN_SOURCE=500 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -D__EXTENSIONS__ -D__SIZE_TYPE__=unsigned int -D__PTRDIFF_TYPE__=int -D__WCHAR_TYPE__=long int -D__WINT_TYPE__=long int -D__GCC_NEW_VARARGS__ -Acpu=sparc -Amachine=sparc less.cc -D__GNUG__=3 -D__DEPRECATED -D__EXCEPTIONS -quiet -dumpbase less.cc -version -o /var/tmp//cc9DmnFo.s
GNU CPP version 3.2.2 (cpplib) (sparc ELF)
GNU C++ version 3.2.2 (sparc-sun-solaris2.8)
	compiled by GNU C version 3.2.2.
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/home/team02/jakan/gnu/sparc-sun-solaris2.8/include"
#include "..." search starts here:
#include <...> search starts here:
 /home/team02/jakan/gnu/include/c++/3.2.2
 /home/team02/jakan/gnu/include/c++/3.2.2/sparc-sun-solaris2.8
 /home/team02/jakan/gnu/include/c++/3.2.2/backward
 /home/team02/jakan/gnu/include
 /home/team02/jakan/gnu/lib/gcc-lib/sparc-sun-solaris2.8/3.2.2/include
 /usr/include
End of search list.
less.cc: In function `bool f(const char*, const char*, const char*)':
less.cc:12: parse error before `,' token
-----------------------------------------
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2003-03-28 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 18:36 jkanze [this message]
2003-03-28 21:06 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=20030328172433.7684.qmail@sources.redhat.com \
    --to=jkanze@caicheuvreuse.com \
    --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).