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

The Archive Base Latest Questions

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

In an objective-c class that can be initialized through different init… methods, it is

  • 0

In an objective-c class that can be initialized through different init… methods, it is common sense to collect initialization code that is common to all initializers into one common method that is called from the other init* methods (or also sometimes from awakeFromNib).

Is there a convention for how this method should be named? initializer? initCommon? …?

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

    According to Apple, initializer methods should always begin with the word ‘init,’ followed by name components that describe the arguments. If a class has more than one initializer, the methods should be chained together so that only one of them is doing all the work, and the others should simply provide default values for the missing arguments.

    So for example, a Person class might have the following init… methods:

    - (id)init
    {
        return [self initWithFirstName:nil
                              lastName:nil];
    }
    
    - (id)initWithFirstName:(NSString *)firstName
                   lastName:(NSString *)lastName
    {
        return [self initWithFirstName:firstName
                              lastName:lastName
                                   age:nil];
    }
    
    - (id)initWithFirstName:(NSString *)firstName
                   lastName:(NSString *)lastName
                        age:(NSNumber *)age
    {
        [super init];
    
        self.firstName = firstName;
        self.lastName = lastName;
        self.age = age;
    
        return self;
    }
    

    UPDATE

    As @dreamlax points out, Apple’s documentation recommends (and when compiling with ARC, the compiler requires) reassigning self with the return value from the call to [super init].

    The docs also recommend checking for nil before performing any further initialization That’s because if the call to [super init] returns nil, self would already have been deallocated by the time the call returns, so there would no longer be an instance to initialize.

    Apple’s documentation also suggests avoiding calls to accessor methods in init... methods; instead, they recommend directly setting the instance variables. So the initWithFirstName:lastName:age: method shown above should ideally be written in a manner similar to the following example:

    - (id)initWithFirstName:(NSString *)firstName
                   lastName:(NSString *)lastName
                        age:(NSNumber *)age
    {
        self = [super init];
    
        if (self == nil) return nil;
    
        _firstName = [firstName copy];
        _self.lastName = [lastName copy];
        _age = [age copy];
    
        return self;
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

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

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

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

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

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer It depends. Many developers define their app log file to… May 13, 2026 at 8:45 pm
  • Editorial Team
    Editorial Team added an answer Regex to find lines with a single word: ^(\w+)$ replace… May 13, 2026 at 8:45 pm
  • Editorial Team
    Editorial Team added an answer NAnt will compile this C# script exactly once when the… May 13, 2026 at 8:45 pm

Related Questions

I'm teaching myself Objective-C from a book ( Cocoa programming for mac OS X
I've set up an Objective-C category for an iPhone app's UIImageView class. The category's
I'm new to Objective-C and Cocoa. I've read that NSInteger and NSNumber are preferred
I've heard now from several sources (stackoverflow.com, cocoa-dev, the documentation, blogs, etc) that it
I am very new to objective-c and having a problem to initialize an object

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.