• 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: Loading 2 classes with same name
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Loading 2 classes with same name


  • Subject: Re: Loading 2 classes with same name
  • From: Wade Tregaskis <email@hidden>
  • Date: Fri, 8 Aug 2003 10:47:18 +1000

I have read that when loading a class that already has that name in use that the behavior is undefined.

Loading the same class twice will usually crash your app. If you've managed to load a class that already existed in the app without crashing, you got lucky.

What would happen then if your app loads a bundle that includes a conflicting class name, possibly from a previous bundle? Isn't poor behavior to crash a whole app because of one bundle? Surely some other action could be taken, like just using the existing class, raising an exception, etc etc.

Wade Tregaskis
-- Sed quis custodiet ipsos custodes?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Loading 2 classes with same name (From: John Randolph <email@hidden>)

  • Prev by Date: Re: Objective-C or C++ or something...
  • Next by Date: Re: Anything bad about allocWithZone: [self zone]?
  • Previous by thread: Re: Loading 2 classes with same name
  • Next by thread: Re: Loading 2 classes with same name
  • Index(es):
    • Date
    • Thread