module api: expose box region
It is the better alternative to linking the small library directly to a module. Why not just use the small library in a module? Functions from an executable are preferred over ones that are shipped in a dynamic library (on Linux, Mac OS differs), while a module may use the small library directly. It may cause a problem when some functions from the library are inlined, but some are not, and those different versions of the library offer structures with different layouts. Small library symbols may be exported by the tarantool executable after the change of default symbols visibility (see [1]). See more details and examples in [2]. So it is better to expose so called box region and get rid of all those compatibility problems. [1]: 2.5.0-42-g03790ac55 ('cmake: remove dynamic-list linker option') [2]: https://lists.tarantool.org/pipermail/tarantool-discussions/2020-September/000095.html Part of #5273
Showing
- src/exports.h 4 additions, 0 deletionssrc/exports.h
- src/lib/core/fiber.c 30 additions, 0 deletionssrc/lib/core/fiber.c
- src/lib/core/fiber.h 82 additions, 0 deletionssrc/lib/core/fiber.h
- test/app-tap/module_api.c 84 additions, 0 deletionstest/app-tap/module_api.c
- test/app-tap/module_api.test.lua 1 addition, 1 deletiontest/app-tap/module_api.test.lua
Loading
Please register or sign in to comment