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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T05:10:19+00:00 2026-05-27T05:10:19+00:00

When synthesizing properties in Objective-C, it’s recommended that you dont simply write: @synthesize window;

  • 0

When synthesizing properties in Objective-C, it’s recommended that you dont simply write:

@synthesize window; 

but rather

@synthesize window = _window;

The reasoning is that you don’t want your instance variable named the same as your getter method or “bad things can happen”.

I’ve always used @synthesize var1, var2, etc in my apps without “bad things” happening. What sort of bad things could happen?

  • 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-27T05:10:20+00:00Added an answer on May 27, 2026 at 5:10 am

    Bad things used to happen, particularly in the pre-ARC days when people would assign objects to the storage iVar instead of the property. If this was done by accident, then the memory management implied by the synthesized setter wouldn’t be applied, leading to leaks, or premature releases.

    I use to do it the simple way, but now I use prefixes. I don’t declare my iVar themselves anymore, I let the modern runtime take care of that for me. I use prefixes so that I don’t accidentally use an iVar like a local variable.

    Also – I tend to refer to my properties as self.iVar almost everywhere in my classes. This is so that I can use lazy loaded properties when I want to without worrying about which ones are and are not lazily loaded.

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

Sidebar

Related Questions

I understand what basic synthesizing does in objective C but I don't understand what
I have a couple strings that I'm synthesizing: .h @property(nonatomic,copy) NSString* bio; .m @synthesize
properties for synthesizing the property : retain / assign retain - it is retained,
Are there any open source, open content projects that use recorded speech data to
I've got a simple question about objective-c. I've been taught to lazily instantiate my
I've a NSMutableArray in AppDelegate I'm using property (nonatomic,retain) and synthesizing it again in
I've seen many examples of Python decorators that are: function style decorators (wrapping a
I've kind of been confused about properties. Some people say to always use setters
I a few simple questions to make sure I am using properties right in
Note: Typically in a dealloc method you should release object instance variables directly (rather

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.