• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "Not really an lvalue" warnings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Not really an lvalue" warnings


  • Subject: Re: "Not really an lvalue" warnings
  • From: "Mark Wagner" <email@hidden>
  • Date: Fri, 6 Apr 2007 15:58:00 -0700

On 4/6/07, James Gregurich <email@hidden> wrote:

What you are trying to do is very bad practice. if the GetText() member function is mandating that the returned character array not have its contents changed, then you should honor that.

It's not *my* code. I'm busy trying to port someone else's code from CodeWarrior to Xcode, and getting all sorts of warnings and errors that I've never seen before.

If you really want to strip the const-ness (even though you
shouldn't), then you do a const_cast<>() on the right side of the
expression to strip the const rather than trying to cast the left
side to be const.

Thanks. I'll work on modifying the code to deal with the strings being const.

--
Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >"Not really an lvalue" warnings (From: "Mark Wagner" <email@hidden>)
 >Re: "Not really an lvalue" warnings (From: James Gregurich <email@hidden>)

  • Prev by Date: Re: "Not really an lvalue" warnings
  • Next by Date: Re: pointer address changes for no reason
  • Previous by thread: Re: "Not really an lvalue" warnings
  • Next by thread: Re: "Not really an lvalue" warnings
  • Index(es):
    • Date
    • Thread