Sack Library Documentation
ContentsIndexReferenceHome
PreviousUpNext
sack_types.h

Define most of the core types on which everything else is based. Also defines some of the primitive container structures. We also handle a lot of platform/compiler abstraction here. 

 

This is automatically included with stdhdrs.h; however, when including sack_types.h, the minimal headers are pulled. stdhdrs.h

Name 
Description 
formatting macro defintions for [vsf]printf output of the above types 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
this symbols is defined to enforce the C Procedure standard - using a stack, and resulting in EDX:EAX etc... 
Method to declare functions exported from a DLL. (nothign on LINUX or building statically, but __declspec(dllimport) on windows ) 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
This is macro IMAGE_LIBRARY_SOURCE. 
method to define a function which will be Imported from a library. Under windows, this is probably __declspec(dllimport). Under linux this is probably 'extern'. 
This is macro LITERAL_LIB_EXPORT_METHOD. 
This is macro LITERAL_LIB_IMPORT_METHOD. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
private thing left as a note, and forgotten. some compilers did not define offsetof 
include this before anything else thereby allowing us to redefine exit() 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
used when the keword specifying a structure is packed needs to prefix the struct keyword. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
This is macro RENDER_LIBRARY_SOURCE. 
Defined for building visual studio monolithic build. These symbols are not relavent with cmakelists. 
declare composite SACK_CONTAINER namespace to declare sack::container::list in a single line 
declare composite SACK_CONTAINER namespace to close sack::container::list in a single line 
declare composite SACK_CONTAINER namespace to declare sack::container in a single line 
declare composite SACK_CONTAINER namespace to close sack::container in a single line 
Could also consider defining 'SACK_NAMESPACE' as 'extern "C" ' {' and '..._END' as '}' 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
This is macro SERVICE_SOURCE. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. and not NO_SQL and not NO_OPTIONS 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Define the container namespace (when building with C++, the wrappers are namespace{} instead of extern"c"{} ) 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. #define SEXPAT_SOURCE Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. 
Defined when SACK_BAG_EXPORTS is defined. This was an individual library module once upon a time. define RENDER SOURCE when building monolithic. 
Name 
Description 
sack 
Render provides a method to display images on a screen. It is the interface between memory images and the window desktop or frame buffer the user is viewing on a monitor.

Under windows, this is implemented as an HWND and an HBITMAP used to allow the application to draw. Updates are done directly from the drawable surface to the HWND as appropriate for the type of service. This is implemented with Vidlib.dll.

Under Linux, this is mounted against SDL. SDL, however, does not give multiple display surfaces, so a more direct method should be used someday, other than SDL does... more 
Created with a commercial version of Doc-O-Matic. In order to make this message disappear you need to register this software. If you have problems registering this software please contact us at support@toolsfactory.com.
Copyright (c) 2000+. All rights reserved.
What do you think about this topic? Send feedback!