Re: Path names in executable
Re: Path names in executable
- Subject: Re: Path names in executable
- From: "Shawn Erickson" <email@hidden>
- Date: Tue, 4 Apr 2006 11:41:40 -0700
On 4/4/06, Erik Buck <email@hidden> wrote:
> Path names in your executable are the least of your worries. Run class-dump sometime. Try F-Script Anywhere. Objective-C is a very dynamic language, and the runtime preserves a lot of information about objects. It is possible to find the name of every class, category, protocol, method, and instance variable in a compiled Objective-C executable. If you think it is unacceptable to embed paths in the executables, you may not want to use Objective-C at all.
Yes I know about Objective-C ... what you point out is an unrelated
issue to want I was concerned about and I am not here to argue this
point but...
Say I release a product A to the public that happens to compile in
some code from product B but product B isn't announced yet. The
existence of those paths in the source code could tip off the
competition, etc. unless one takes steps to stage source before it is
compiled.
Also Stefan brings up a valid side effect of this behavior (note sure
how to address this issue...).
In theory strip could rewrite those after the final link of the
release product (note sure how they play in dynamic linking).
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden