#239 VOS: Problematic type definitions

[Bernd Brandstetter]

Apart from the question if it was a good idea to introduce own type definitions (UINT8/16/32...) instead of just using the standardized C99 types, the problem is that vos_types.h insists on defining all these data types on its own, making it impossible to use VOS on (embedded) systems which either already provide matching type definitions or don't have stdint.h.

A more generic approach would be to let vos_types.h include a custom header file which must be provided by the user and contain all requires type definitions.

#if (defined (WIN32) || defined (WIN64))
// provide type definitions for Windows systems
#elif defined(POSIX)
// provide type definitions for POSIX systems
#elif defined(VXWORKS)
// provide type definitions for VxWorks
#elif defined(INTEGRITY)
// provide type definitions for Inegrity
#else
  #include "custom_types.h"
#endif**

[Bernd Löhr]

Bernd, the type definitions are (unfortunately) part of the standard (IEC61375-1 and -2-3). And: C99 was too new for M$ VS 2010 to be used (which was the first compiler AHW used when the project started...) – so we actually had to use C89 ;-(

When targeting a new HW/SW, apart from adding specialized target folder, one has to change vos/api header files anyway...
Regards

[Bernd Löhr]

Each new target requires a review of vos_types.h, anyway.