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

  • SEARCH
  • Home
  • 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 598785
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T16:25:37+00:00 2026-05-13T16:25:37+00:00

I’m still getting confused by Objective-C. Sometimes you declare a variable like so: NSRect

  • 0

I’m still getting confused by Objective-C. Sometimes you declare a variable like so:

NSRect rect;

And sometimes like so:

NSValue *value;

I never know when to add the *, so far I always looked it up in Apple’s documentation. I know the difference is between a value and a pointer to an object.

But are there any hard and fast rules as to when I declare a value and when I declare a pointer? Something to make it easier to remember? Or do I have to know (eg. look up) which NSSomething is a value and which is an object?

Thank you!

  • 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-13T16:25:37+00:00Added an answer on May 13, 2026 at 4:25 pm

    Short and simple: yes, you have to remember this for each type, but it will come very naturally after a little while.

    It’s not so much a question of “which NSSomething is a value and which is an object” (more accurately: which NSSomething is a scalar datatype or a struct and which is a class), though. Even though you won’t see or use declarations like:

    NSRect *pointerToARect;
    NSInteger *pointerToAnInteger;
    

    very often, they are perfectly valid and necessary at times. So for scalars (simple datatypes like NSInteger) and structs, both variants are valid and which one you use depends on whether you need a pointer or the actual thing.

    With objects, all your variables must always be pointers because objects can only be allocated on the heap and not on the stack. So unlike the examples above, this:

    NSValue myValue; // invalid!
    

    is not correct and will not compile.

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

Sidebar

Ask A Question

Stats

  • Questions 378k
  • Answers 378k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer Eineki cracked the algorithm. The part missing from my attempts… May 14, 2026 at 9:19 pm
  • Editorial Team
    Editorial Team added an answer My first guess is that the parameter ReferenceAssemblies is null.… May 14, 2026 at 9:19 pm
  • Editorial Team
    Editorial Team added an answer Just add ON UPDATE CASCADE to the foreign key constraint. May 14, 2026 at 9:19 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.