• 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: C++ name collisions between plugins
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: C++ name collisions between plugins


  • Subject: Re: C++ name collisions between plugins
  • From: Paul Miller <email@hidden>
  • Date: Thu, 15 Aug 2013 12:40:30 -0500
  • Organization: FXTECH

On 8/15/2013 12:05 PM, Peter Litwinowicz wrote:
Paul,

Have you run
nm -a
On the resultant binary to make SURE that the requisite
structures/classes are hidden?

No, I haven't done that. Good advice.

I've found that symbols are not necessarily hidden  unless you hide the
symbols upon compile (using the hidden flag for visibility), and THEN
also strip the binary afterwards.

Yes, I'm not stripping in debug mode - which could account for the collisions I'm seeing there. As long as release builds are fully locked down, I'll be happy.

Will give nm a try thanks! I just mostly wanted to make sure that it was ACTUALLY doable, without massive namespace changes.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Re: C++ name collisions between plugins (From: Peter Litwinowicz <email@hidden>)

  • Prev by Date: Re: C++ name collisions between plugins
  • Next by Date: Re: C++ name collisions between plugins
  • Previous by thread: Re: C++ name collisions between plugins
  • Next by thread: Re: C++ name collisions between plugins
  • Index(es):
    • Date
    • Thread