Re[4]: NSString changes breaks...

[Manuel Guesdon]

On Tue, 31 Oct 2000 20:47:11 +0000 you wrote:
 >| I agree - I can't see how it could have worked.  I grabbed a three week old 
 >version of gstep-base
 >| from CVS, and looked at the source, and it doesn't look as though anything 
 >has changed that should
 >| effect this (though I could easily have missed some subtle bug I suppose).

May be. I have'nt found any reason too. White magic.


 >| However, for your purposes, as far as I can see, you don't need a subclass 
 >at all -
 >| what you want is simply to add a category to NSMutableString so that *all* 
 >mutable
 >| string objects will have your methods available.  The code change required 
 >to do this
 >| is trivial and your existing method implementations should not need to 
 >change.

I finally use this method. 
Intellectually, it's not very satisfaisant: 
        o with this way, we can't do a NSClassFromString(@"GSWElementIDString");
        o choosing to reimplement a basic MutableString is not the solution 
because we can make stupid mistake when rewriting such code and because good 
developers don't code 2 times the same thing :-)

Anyway,n I'll (try to) live with this :-)

Manuel
--