On Dec 9, 2006, at 9:35 AM, Alfred Van Hoek wrote:
On Oct 25, 2006, at 11:32 AM, Jonathan Johnson wrote:
Well, here's the issue. It turns out this is the problem. We use
NSAddImage and NSLookupSymbolInImage because dyld isn't available
in anything prior to 10.3. NSAddImage has no notion of adding an
image to a private namespace, even if two level namespaces are
used. So, whichever library loads the symbol first will be used
for the rest of the run.
We can use dyld on 10.3 and higher though, so if possible, please
file a report against this. One workaround might be to package the
dylib into a bundle and declare against the bundle. This should work.
Does this still holds? I mean it is an issue that I have. If
REALbasic is adding an image to a private namespace, our code will
fail to add it's own image, and when we call a symbol, it is the
symbol owned by the rbframework that will crash our app. (Using the
current RB version in 10.4.8).
Yes and no. For soft declares, it still does matter. For plugins, you
can build your plugin as a Bundle instead of a Dylib (not an actual
folder bundle, just a Mach-O bundle). As of 2006r4 we support these
library types, and back to 10.1 they have a private namespace.
HTH,
Jon
--
Jonathan Johnson
jonj at realsoftware dot com
REAL Software, Inc.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|