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: Re: Problem with class operators.
Date: Mon, 25 Jul 2005 12:06:00 -0000	[thread overview]
Message-ID: <fc.0000000100014e603b9aca0075893219.14e61@KielNet.net> (raw)
In-Reply-To: <BF0A3AC0.2E9%eljay@adobe.com>

Hi Eljay,

thanks, I thought so. I saw in MFC, that this stuff works for the CString
class (with LPSTR, what comes to char* after several "show define"). I
think great, if you like to use the object directly in functions, which
want an char*. But seem to be VS special stuff (CW couldn't handle this
too).

kind regards,

Kristian

Eljay Love-Jensen <eljay@adobe.com> on Montag, 25. Juli 2005 at 13:44
+0100 wrote:
>Hi Kristian,
>
>When you have an ambiguous situation like that, you could try this:
>
>b = (ckstring.operator == (pchar));
>
>Or you could remove the implicit convenience cast (operator char*), to
>something like this, like was done with std::string for the same reason:
>
>char* CkString::c_str();
>
>HTH,
>--Eljay
>
>
>



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

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


  reply	other threads:[~2005-07-25 12:06 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 ` Problem with class operators Kristian Kratzenstein
2005-07-25 11:44   ` Eljay Love-Jensen
2005-07-25 12:06     ` Kristian Kratzenstein [this message]
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.0000000100014e603b9aca0075893219.14e61@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).