Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Install wx/cocoa/objc/objc_uniquifying.h for wxCocoa and add a usage note

Browse Source 
to the header.
Copyright 2007 Software 2000 Ltd.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@48068 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
David Elliott
2007-08-14 20:39:50 +00:00
parent 5a617be899
commit 6c67fde0b8
3 changed files with 42 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
include/wx/cocoa/objc/objc_uniquifying.h
View File

@@ -15,6 +15,28 @@
#ifndef __WX_COCOA_OBJC_CLASS_H__
#define __WX_COCOA_OBJC_CLASS_H__
/* A note about this header:
Nothing in here is guaranteed to exist in future versions of wxCocoa. There
are other ways of adding Objective-C classes at runtime and a future wxCocoa
might use these instead of this ugly hack. You may use this header file in
your own wxCocoa code if you need your own Objective-C classes to be
unqiuified.
You cannot turn this on for 64-bit mode. It will not compile due to opaque
Objective-C data structures and it is not needed because it is a workaround
for a bug that does not exist in the 64-bit runtime.
You should not use this when wxCocoa is built as a dynamic library. This has
only been tested for the case when wxCocoa is built as a static library and
statically linked to user code to form a loadable bundle (e.g. a Cocoa plugin).
It forces each plugin (when multiple wxCocoa-using plugins are used) to use
its own internal Objective-C classes which is desirable when wxCocoa is
statically linked to the rest of the code.
Do not use uniquifying on your principal class. That one should be named
differently for different bundles.
*/
#if wxUSE_OBJC_UNIQUIFYING
// objc_getClass and stuff