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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T10:11:12+00:00 2026-05-21T10:11:12+00:00

Is it necessary to release a NSPipe created writing NSPipe *pipe = [NSPipe pipe];

  • 0

Is it necessary to release a NSPipe created writing

NSPipe *pipe = [NSPipe pipe];

?
Actually I do not call alloc so theoretically I should not call release…Am I right?

  • 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-21T10:11:13+00:00Added an answer on May 21, 2026 at 10:11 am

    Yes, you’re right. As usual, the memory management rules apply: if you’ve obtained an object via a method that isn’t NARC (name contains new, alloc, copy, or is retain), then you don’t own that object, hence you don’t release it.

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

Sidebar

Related Questions

The Castle wiki says at several places I should ALWAYS call container.Release() for components
Why UIButton does not require to alloc and init call instead we use only
Right now the Release build just makes the files necessary for the install. But
Is it really necessary to release COM components from Office PIA, when you don't
I'm wondering how to make a release build that includes all necessary DLL files
not necessary an UML diagram, just a simple way to graphically document the relations
Is it necessary for me to call allocator.construct() for an array of primitive types
Is the following true? When the app is about to quit, it's not necessary
when i call: ChooseDateView *nextController = [[ChooseDateView alloc] initWithNibName:@ChooseDateView bundle:nil]; [self.navigationController pushViewController:nextController animated:YES]; is
I'm wondering for a class like the following , is that necessary to call

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.