|
Size: 1328
Comment: update content - tip in address
|
Size: 1588
Comment: add search exclusions for SG pages; a little pre-editing
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| '''Include File(s):''' [[http://hg.libsdl.org/SDL/file/tip/include/SDL_loadso.h|SDL_loadso.h]] | '''Include File(s):''' [[http://hg.libsdl.org/SDL/file/default/include/SDL_loadso.h|SDL_loadso.h]] |
| Line 17: | Line 17: |
| ^There are some^ ,,S,,ystem dependent library loading routines. . ,,Some,, things to keep in mind: |
There are some system dependent library loading routines. . Things to keep in mind: |
| Line 21: | Line 21: |
| * Avoid namespace collisions. If you load a symbol from the library, it is not defined ,,whether or not,, ^as to whether^ it goes into the global symbol namespace for the application ^or not^. If it does and it conflicts with symbols in your code or other shared libraries, you will not get the results you expect. :) ''or'' ;) | * Avoid namespace collisions. If you load a symbol from the library, it is not defined as to whether it goes into the global symbol namespace for the application or not. If it does and it conflicts with symbols in your code or other shared libraries, you will not get the results you expect. ##Remove this line and the ## below to use this markup if it becomes relevant to this category ##== Enumerations == ##<<FullSearch(category:CategoryEnum CategorySharedObject -SGEnumerations)>> ##== Structures == ##<<FullSearch(category:CategoryStruct CategorySharedObject -SGStructures)>> |
| Line 24: | Line 31: |
<<FullSearch(category:CategorySharedObject -CategoryEnum -CategoryStruct)>> |
<<FullSearch(category:CategorySharedObject -CategoryEnum -CategoryStruct -SGFunctions)>> |
DRAFT |
Shared Object Loading and Function Lookup
Include File(s): SDL_loadso.h
Introduction
This category contains functions for handling shared objects and additional functions.
There are some system dependent library loading routines.
- Things to keep in mind:
- These functions only work on C function names. Other languages may have name mangling and intrinsic language support that varies from compiler to compiler.
- Make sure you declare your function pointers with the same calling convention as the actual library function. Your code will crash mysteriously if you do not do this.
- Avoid namespace collisions. If you load a symbol from the library, it is not defined as to whether it goes into the global symbol namespace for the application or not. If it does and it conflicts with symbols in your code or other shared libraries, you will not get the results you expect.
