Home/ Questions/Q 7545787
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T09:01:17+00:00

I assign here on a an Object a derivative of the same object. Is

  • 0

I assign here on a an Object a derivative of the same object. Is there any problem with this?

NSString *urlString =[TBXML textForElement:tempElement];
urlString = [urlString stringByReplacingOccurrencesOfString:@" " withString:@"%20"];
urlString = [urlString stringByReplacingOccurrencesOfString:@"&" withString:@"&"];
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, that’s fine. After running this code, there will be three NSString objects in memory:

    1. The one created by [TBXML textForElement:tempElement]
    2. The one created by [urlString stringByReplacingOccurrencesOfString:@" " withString:@"%20"]
    3. The one created by [urlString stringByReplacingOccurrencesOfString:@"&" withString:@"&"]

    Each of them will have a retain count of 1 but will be autoreleased. Since you don’t keep references to 1. or 2., there’s no way you’ll be able to increase their retain counts afterwards, so at the end of the current iteration of the run loop they will be autoreleased, their retain counts will go to 0, and they will be deallocated.

    The third one is in the same boat, but you do have a reference to it, so if you do something to increase its retain count (e.g., assign it to a strong @property or add it to an NSArrray) then it may continue to exist after this iteration of the run loop. Or, if you’re just using it as a parameter to some function (maybe you just use it in NSString stringWithFormat: later on, it will get deallocated along with the other two.

    • 0