• 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: ObjC's flat and all-exported namespace, help!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ObjC's flat and all-exported namespace, help!


  • Subject: Re: ObjC's flat and all-exported namespace, help!
  • From: Karl Goiser <email@hidden>
  • Date: Wed, 09 Nov 2011 20:11:23 +1100

.. so if you prefix all your classes with your company name, the only conflicts will be with the same class from different bundles, which means that only one instance of any class will be loaded, thus saving memory on every client’s machine…

Yes?


On 09/11/2011, at 7:14 PM, Andy O'Meara wrote:

>
>
> Unfortunately the problem is that when you sell and ship commercial software, shipped software can't look into the future.  The real aspect of this issue, that I raised in my initial post, is that third party developers such as ourselves internally reuse various support classes for multiple bundle products, so when the host loads our products this issue surfaces.
>
> And yes, this thread does belong on the objC list and will be moving it there (I didn't realize there was a objC list when I originally posted).
>
>
>
> On Nov 9, 2011, at 12:08 AM, Karl Goiser wrote:
>
>> I think there is another solution that doesn’t involve making the language more complicated:
>>
>> I would complain to the suppliers of the bundles with conflicting class names.
>>
>> They know they are delivering into an environment with a flat namespace.  It is up to them to defend against this sort of problem.  It’s their fault that this problem is occurring.
>>
>>
>> Karl
>>
>> _______________________________________________
>>
>> 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
>

_______________________________________________

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: ObjC's flat and all-exported namespace, help!
      • From: Andreas Grosam <email@hidden>
    • Re: ObjC's flat and all-exported namespace, help!
      • From: Jean-Daniel Dupas <email@hidden>
References: 
 >ObjC's flat and all-exported namespace, help! (From: Andy O'Meara <email@hidden>)
 >Re: ObjC's flat and all-exported namespace, help! (From: Greg Parker <email@hidden>)
 >Re: ObjC's flat and all-exported namespace, help! (From: Ian Joyner <email@hidden>)
 >Re: ObjC's flat and all-exported namespace, help! (From: Jean-Daniel Dupas <email@hidden>)
 >Re: ObjC's flat and all-exported namespace, help! (From: John Joyce <email@hidden>)
 >Re: ObjC's flat and all-exported namespace, help! (From: Karl Goiser <email@hidden>)
 >Re: ObjC's flat and all-exported namespace, help! (From: Andy O'Meara <email@hidden>)

  • Prev by Date: Re: NSFileHandle readInBackground vs threading?
  • Next by Date: Re: Allocating too much memory kills my App rather than returning NULL
  • Previous by thread: Re: ObjC's flat and all-exported namespace, help!
  • Next by thread: Re: ObjC's flat and all-exported namespace, help!
  • Index(es):
    • Date
    • Thread