public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kristian Kratzenstein" <kristian.kratzenstein@kielnet.net>
To: gcc-help@gcc.gnu.org
Subject: Problem with class operators.
Date: Mon, 25 Jul 2005 08:26:00 -0000	[thread overview]
Message-ID: <fc.0000000100014e563b9aca0075893219.14e57@KielNet.net> (raw)
In-Reply-To: <42E49A30.9060800@kangaroologic.com>

Hi All,

I've a problem with class operators. In this case (I try to cut this down)
my class, which holds a string.
I'm working on XCode.

	bool CkString::operator == (char const* string);

	CkString::operator char*();

Now I try :

	b = (ckstring == pchar);

now I get an Error :  

	error : ISO C++ says that these are ambiguous, even the worst
conversation for the first is better than the worst conversation for the
second
	note : candidate 1: bool CkString::operator==(const char*)
	note : candidate 2: operator==(char*, char*) <built-in>

thanks for help,

Kristian

--------------------------------------------
Kristian Kratzenstein
Gettorf

Kristian.Kratzenstein@KielNET.net
--------------------------------------------


  reply	other threads:[~2005-07-25  8:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  7:50 Which ELF platforms support visibility attribute? Jonathan Turkanis
2005-07-25  8:26 ` Kristian Kratzenstein [this message]
2005-07-25 11:44   ` Problem with class operators Eljay Love-Jensen
2005-07-25 12:06     ` Kristian Kratzenstein
2005-07-25 15:17     ` Kristian Kratzenstein
2005-07-25 15:32       ` Eljay Love-Jensen
2005-07-25 17:47         ` Kristian Kratzenstein
2005-07-25 18:00           ` Eljay Love-Jensen
2005-07-25 18:13           ` corey taylor
2005-07-25 19:02             ` Kristian Kratzenstein
2005-07-25 19:07               ` corey taylor
2005-07-25 19:32               ` Eljay Love-Jensen
2005-07-25 15:49       ` corey taylor

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=fc.0000000100014e563b9aca0075893219.14e57@KielNet.net \
    --to=kristian.kratzenstein@kielnet.net \
    --cc=gcc-help@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).