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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T01:56:47+00:00 2026-05-18T01:56:47+00:00

In my code I do, ClassA *reference = [[ClassA alloc] init]; [reference invokeMethod]; reference

  • 0

In my code I do,

ClassA *reference = [[ClassA alloc] init];
[reference invokeMethod];
reference = nil;
[reference release];

Without the reference = nil I know it releases the memory cos its normal way to do so. But in this situation if we make the reference nil and release the memory later does it remove the earlier memory consumed for object creation?

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-18T01:56:48+00:00Added an answer on May 18, 2026 at 1:56 am

    No. release = nil just makes the memory it originally points to unaccessible; it won’t remove the memory consumed. (Also, this causes the [reference release]; statement afterward a no-op.)

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

Sidebar

Related Questions

I have the following: classA::FuncA() { ... code FuncB(); ... code } classA::FuncB(const char
Which of these pieces of code is faster? if (obj is ClassA) {} if
I'm almost there understanding simple reference counting / memory management in Objective-C, however I'm
Why is the following code causing a memory leak in an iPhone App? All
If I have Python code class A(): pass class B(): pass class C(A, B):
Considering such code: class ToBeTested { public: void doForEach() { for (vector<Contained>::iterator it =
I have the following code: class IncidentTag: def __init__(self,tag): self.tag = tag def equals(self,obj):
Here's my code: class Publisher(models.Model): name = models.CharField( max_length = 200, unique = True,
Why does this code: class A { public: explicit A(int x) {} }; class
When I try this code: class MyStuff: def average(a, b, c): # Get the

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.