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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T13:21:43+00:00 2026-05-27T13:21:43+00:00

Is calling [myObject performSelector:@selector(something) withObject:nil]; the same as just calling [myObject performSelector:@selector(something)]; ?

  • 0

Is calling [myObject performSelector:@selector(something) withObject:nil]; the same as just calling [myObject performSelector:@selector(something)];?

  • 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-27T13:21:43+00:00Added an answer on May 27, 2026 at 1:21 pm

    The only difference is signature of the method you intend on calling from the @selector. Use performSelector when the method takes no arguments, and use performSelector:withObject if the method takes a single argument of type id. Otherwise, they both do the exact same thing.

    From the NSObject Protocol Reference:

    Discussion

    This method is the same as performSelector: except that you
    can supply an argument for aSelector. aSelector should identify a
    method that takes a single argument of type id. For methods with other
    argument types and return values, use NSInvocation.

    As Chuck points out, this isn’t really enforced (at least not at this point in time). The code below executed fine without any exceptions being thrown at me.

    -(void)viewDidLoad
    {
        [super viewDidLoad];    
        [self performSelector:@selector(foo) withObject:nil];
    }
    -(void)foo
    {
        NSLog(@"foo!");
    }
    

    On the other hand, this version of the code did cause problems. So it doesn’t work both ways.

    -(void)viewDidLoad
    {
        [super viewDidLoad];    
        [self performSelector:@selector(foo)];
    }
    -(void)foo:(id)myParameter
    {
        NSLog(@"foo!");
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I must have misunderstood something. I simply want to use performSelector: to call one
I am trying to update some object properties by calling UpdateModel(myObject, new[] { "stringprop1",
Possible Duplicate: why does initializing subclasses require calling the super class's same init function?
I have two threads modifying the same object, lets say MyObject, and so have
I can get the unique id like className@2345 of my object by calling its
Calling Validate() on an XmlDocument requires passing in a ValidationEventHandler delegate. That event function
Calling all C macro gurus... Is there any way to write a C macro
Calling TextRenderer.MeasureText as follows: TextRenderer.MeasureText(myControl.Text, myControl.Font); and comparing the result to the size of
Calling image = Image.open(data) image.thumbnail((36,36), Image.NEAREST) will maintain the aspect ratio. But I need
Calling Html.RenderPartial(~/Views/Payments/MyControl.ascx); from a view works if MyControl.ascx is a control that directly inherits

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.