• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Strategies to prevent class name clashes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strategies to prevent class name clashes


  • Subject: Re: Strategies to prevent class name clashes
  • From: Arne Scheffler <email@hidden>
  • Date: Sat, 16 Feb 2008 09:18:10 +0100

Thanks all, for your comments and ideas how to solve this issue.
After all the only workable solution to this problem is to create the Objective-C classes at runtime.
As B.J. already said this is only glue code which only consists of 5 Objective-C classes. But even with this few classes it's much work to convert my already written code to this mimic. I can only hope that no one else need to do this kind of ugly work. But for the ones who need, look at the "Objective-C 2.0 Runtime Reference" or at <objc/runtime.h> file.


arne

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Strategies to prevent class name clashes
      • From: Chris Hanson <email@hidden>
References: 
 >Strategies to prevent class name clashes (From: Arne Scheffler <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: Lieven Dekeyser <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: Uli Kusterer <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: Arne Scheffler <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: Thomas Engelmeier <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: Arne Scheffler <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: Bill Bumgarner <email@hidden>)
 >Re: Strategies to prevent class name clashes (From: "B.J. Buchalter" <email@hidden>)

  • Prev by Date: Setting NSTextField inside drawRect:
  • Next by Date: NSFileManager
  • Previous by thread: Re: Strategies to prevent class name clashes
  • Next by thread: Re: Strategies to prevent class name clashes
  • Index(es):
    • Date
    • Thread