Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6367503
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T00:33:20+00:00 2026-05-25T00:33:20+00:00

Is this pointer assignment correct? customclass.somearray = &*otherarray; where somearray and otherarray are NSArray

  • 0

Is this pointer assignment correct?

customclass.somearray = &*otherarray;

where somearray and otherarray are NSArray objects.
If not, how do I solve my problem:
I want to share this otherarray object with customclass.somearray. And I want all changes
made to customclass.somearray to be made to the original otherarray too.
Doing it this way, it works. I just want to ask, is it correct?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T00:33:20+00:00Added an answer on May 25, 2026 at 12:33 am

    Your two variables are pointers of the same type, so just assign one to the other:

    customclass.somearray = otherarray;
    

    The way you have written this is unnecessary. Using the dereference operator * essentially gives you the “contents” of the pointer. The address-of operator & correspondingly gives you the address of whatever you apply it to. Your pointer otherarray contains an address. If you dereference that address and then take the address of that, you end up right back where you started.

    Be aware that the left side of this assignment is a property access (assuming that customclass is also an object and not just a struct). This means that the compiler will change your expression into:

    [customclass setSomearray:&*otherarray];
    // And my version will be changed into:
    [customclass setSomearray:otherarray];
    

    That is, it becomes a method call rather than a simple assignment. This does not affect the syntax you should use, however.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I hardly see any pointer on the following problem related to Hibernate. This pertains
How should I avoid using the this pointer in conjunction with smart pointers? Are
Hi I have a question about this pointer, when an object is constructed, when
I have a pointer to integer array of 10. What should dereferencing this pointer
This one is quite obviously a function pointer : typedef int (* foobar) (int
This is C4055 Warning message. 'conversion' : from data pointer 'type1' to function pointer
Can I pass this to a function as a pointer, from within the class
This concept seems to trouble me. Why does an NSError object need its pointer
I have a pointer to a map that I am trying to delete (this
I'm getting a warning: Return makes pointer from integer without a cast for this

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.