Not sure if this is the right list, but since it seems to be exclusive
to Obj-C, I'm sending it here.
Recently I've noticed that running the command line program "strings"
against a release build (with debugging or all symbols stripped)
reveals several full paths of source code files, specifically .m
and .mm files; I haven't seen .cpp or .c files show up. Strangely,
it's not all of them, nor can I find any commonality between them. At
one point I thought it was from use of a macro we use around NSLog,
but some files using it don't show up, and some which don't use it do.
I looked for these files in the .pbxproj, but didn't see anything
unusual.
Running strings on other programs showed that other developers,
including Apple, have this issue. I looked at Terminal, Xcode,
Interface Builder, and Twitterrific, and all had 1-5 source file
paths. We have a lot more than that though, around 20.
Does anyone know what causes this, and/or how to prevent it?
-Daniel
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
