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 6224475
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T08:40:46+00:00 2026-05-24T08:40:46+00:00

Possible Duplicate: Properties declared as instance variables too? Let’s say I have an objective

  • 0

Possible Duplicate:
Properties declared as instance variables too?

Let’s say I have an objective c class interface like:

@interface {
     NSString * someString;
}

@property (nonatomic, retain) NSString *  someString;

with an @implementation that @synthesizes the string and does some other stuff.

What I’d like to know is, whether it’s necessary to have that NSString * someString object pointer declaration within the brackets at all. (As an aside, is there a specific term for the space between the brackets where variables are defined?) It seems like the code will work fine if I omit the NSString * someString declaration, and the @property line has all the same information about type. So, if it’s not necessary to have the variable declaration, why does the option exist at all? What happens if you have conflicting types in the variable declaration and the @property declaration?

  • 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-24T08:40:47+00:00Added an answer on May 24, 2026 at 8:40 am

    For the most part, it shouldn’t be necessary, since @synthesize will create a variable if it is not predefined. Also, you can create your own variable with @synthesize as well, using:

    @synthesize aVar = _theVariableName;
    

    That will create a getter method (aVar), a setter method (setAVar), and an instance variable named _theVariableName which you can use for memory management purposes.

    However, I don’t know if @dynamic will do the same, and if implementing your own setters and getters, I think you need the declaration…

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

Sidebar

Related Questions

Possible Duplicate: Comparing object properties in c# Let's say I have a POCO: public
Possible Duplicate: Should I Use self Keyword (Properties) In The Implementation? Say I have
Possible Duplicate: Can Read-Only Properties be Implemented in Pure JavaScript? I have an Object
Possible Duplicate: Objective-C properties: atomic vs nonatomic By default all properties in Objective-C are
Possible Duplicate: Cannot use concatenation when declaring default class properties in PHP? The following
Possible Duplicate: How does the Google Did you mean? Algorithm work? Suppose you have
Possible Duplicate: Properties vs Methods In method you can type some code and in
Possible Duplicate: Properties vs Methods Is there any rule or general best practice as
Possible Duplicate: Properties vs Methods For many situations it is obvious whether something should
Possible Duplicate: C#: Public Fields versus Automatic Properties Duplicate? I think not: This question

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.