comparison README.compat @ 266:53b0e7557c52

...
author cannam
date Thu, 20 Nov 2008 21:51:37 +0000
parents 03c7167e1f30
children
comparison
equal deleted inserted replaced
265:03c7167e1f30 266:53b0e7557c52
78 ---------------------------------- 78 ----------------------------------
79 One of the changes in this version of the SDK is that separate 79 One of the changes in this version of the SDK is that separate
80 top-level C++ namespaces are used for classes compiled into plugins 80 top-level C++ namespaces are used for classes compiled into plugins
81 (the _VampPlugin namespace) and hosts (the _VampHost namespace), to 81 (the _VampPlugin namespace) and hosts (the _VampHost namespace), to
82 avoid any confusion between host and plugin namespaces in unusual 82 avoid any confusion between host and plugin namespaces in unusual
83 linkage situations. This is handled transparently in most 83 linkage situations (as the host and plugin SDKs contain many of the
84 circumstances, and neither plugin nor host authors will normally need 84 same classes, there is a risk that the wrong class may be picked up by
85 to care about it. 85 a stupid dynamic linker in cases where the host and plugin SDK
86 versions do not match). This additional namespace is added and opened
87 silently in a manner that is transparent in most circumstances, and
88 neither plugin nor host authors will normally need to know about it.
86 89
87 However, hosts that directly incorporate code from plugins, for 90 However, hosts that directly incorporate code from plugins, for
88 example to provide functionality that is the same as those plugins 91 example to provide functionality that is the same as those plugins
89 without having to explicitly load them, will find that they cannot 92 without having to explicitly load them, will find that they cannot
90 resolve plugin symbols at link time because of this namespace 93 resolve plugin symbols at link time because of this namespace