Home/ Questions/Q 6474325
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T06:34:27+00:00

One part of the program takes text from a uitextfield, copies it to a

  • 0

One part of the program takes text from a uitextfield, copies it to a mutable string and then performs

     sharedManager.ce_name=name.text


    [sharedManager.ce_name replaceOccurrencesOfString:@" " withString:@"%20"
     options:NSLiteralSearch range:NSMakeRange(0, [sharedManager.ce_name length])];

At this point it always gave me “attempt to mutate immutable object” – it was not random

The first time I got this error I changed it to 

    sharedManager.ce_name=(NSMutableString *)name.text

This STILL gave me the attempt to mutate immutable object error, but it would occur randomly – weird right?

I then changed it to 

    NSMutableString *mutable_name = [NSMutableString stringWithString:name.text];

    sharedManager.ce_name=mutable_name;

It has yet to fail on me doing it this way but I am convinced that I have not found the solution.

my questions:

1) Could that fact that it was doing it randomly after the first fix indicate I have some deep seated memory management problem?

2) Why didn’t the C-style cast fix it?

3) Will my current fix work?

Thanks for your time 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem here is the way in which you’re using casting. When you cast a pointer, it just starts treating the memory at that location as though it were a block of data representing that type.

    So if I’ve got a pointer to a Car class: Car* mycar;, and I cast it to a Person object: (Person*)mycar;, the program will try to access the memory there as though it was pointing at a Person object. However, a car is not a person, except in an old TV sitcom, so when it tries to access members on this or call functions, it’s going to try to go to a memory location that contains something other than what it’s expecting, and undefined things happen (generally, crashing).

    NSMutableString and NSString are incompatible in this regard, and so casting from one to the other will result in terrible times. Your fix ([NSMutableString stringWithString:]) is the correct solution.

    • 0