| … | |
… | |
| 58 | |
58 | |
| 59 | =head2 TYPES / TYPE SUPPORT |
59 | =head2 TYPES / TYPE SUPPORT |
| 60 | |
60 | |
| 61 | ecb.h makes sure that the following types are defined (in the expected way): |
61 | ecb.h makes sure that the following types are defined (in the expected way): |
| 62 | |
62 | |
| 63 | int8_t uint8_t int16_t uint16_t |
63 | int8_t uint8_t int16_t uint16_t |
| 64 | int32_t uint32_t int64_t uint64_t |
64 | int32_t uint32_t int64_t uint64_t |
| 65 | intptr_t uintptr_t |
65 | intptr_t uintptr_t ptrdiff_t |
| 66 | |
66 | |
| 67 | The macro C<ECB_PTRSIZE> is defined to the size of a pointer on this |
67 | The macro C<ECB_PTRSIZE> is defined to the size of a pointer on this |
| 68 | platform (currently C<4> or C<8>). |
68 | platform (currently C<4> or C<8>) and can be used in preprocessor |
|
|
69 | expressions. |
|
|
70 | |
|
|
71 | =head2 LANGUAGE/COMPILER VERSIONS |
|
|
72 | |
|
|
73 | All the following symbols expand to an expressionb that cna be tested in |
|
|
74 | preprocessor instructions as well as treated as a boolean (use C<!!> to |
|
|
75 | ensure it's either C<0> or C<1> if you need that). |
|
|
76 | |
|
|
77 | =over 4 |
|
|
78 | |
|
|
79 | =item ECB_C |
|
|
80 | |
|
|
81 | True if the implementation defines the C<__STDC__> macro to a true value, |
|
|
82 | which is typically true for both C and C++ compilers. |
|
|
83 | |
|
|
84 | =item ECB_C99 |
|
|
85 | |
|
|
86 | True if the implementation claims to be C99 compliant. |
|
|
87 | |
|
|
88 | =item ECB_C11 |
|
|
89 | |
|
|
90 | True if the implementation claims to be C11 compliant. |
|
|
91 | |
|
|
92 | =item ECB_CPP |
|
|
93 | |
|
|
94 | True if the implementation defines the C<__cplusplus__> macro to a true |
|
|
95 | value, which is typically true for C++ compilers. |
|
|
96 | |
|
|
97 | =item ECB_CPP98 |
|
|
98 | |
|
|
99 | True if the implementation claims to be compliant to ISO/IEC 14882:1998 |
|
|
100 | (the first C++ ISO standard) or any later vwersion. Typically true for all |
|
|
101 | C++ compilers. |
|
|
102 | |
|
|
103 | =item ECB_CPP11 |
|
|
104 | |
|
|
105 | True if the implementation claims to be compliant to ISO/IEC 14882:2011 |
|
|
106 | (C++11) or any later vwersion. |
|
|
107 | |
|
|
108 | =item ECB_GCC_VERSION(major,minor) |
|
|
109 | |
|
|
110 | Expands to a true value (suitable for testing in by the preprocessor) |
|
|
111 | if the compiler used is GNU C and the version is the givne version, or |
|
|
112 | higher. |
|
|
113 | |
|
|
114 | This macro tries to return false on compilers that claim to be GCC |
|
|
115 | compatible but aren't. |
|
|
116 | |
|
|
117 | =back |
| 69 | |
118 | |
| 70 | =head2 GCC ATTRIBUTES |
119 | =head2 GCC ATTRIBUTES |
| 71 | |
120 | |
| 72 | A major part of libecb deals with GCC attributes. These are additional |
121 | A major part of libecb deals with GCC attributes. These are additional |
| 73 | attributes that you can assign to functions, variables and sometimes even |
122 | attributes that you can assign to functions, variables and sometimes even |
| … | |
… | |
| 581 | for (i = 0; i < ecb_array_length (primes); i++) |
630 | for (i = 0; i < ecb_array_length (primes); i++) |
| 582 | sum += primes [i]; |
631 | sum += primes [i]; |
| 583 | |
632 | |
| 584 | =back |
633 | =back |
| 585 | |
634 | |
|
|
635 | =head2 SYMBOLS GOVERNING COMPILATION OF ECB.H ITSELF |
| 586 | |
636 | |
|
|
637 | These symbols need to be defined before including F<ecb.h> the first time. |
|
|
638 | |
|
|
639 | =over 4 |
|
|
640 | |
|
|
641 | =item ECB_NO_THRADS |
|
|
642 | |
|
|
643 | If F<ecb.h> is never used from multiple threads, then this symbol can |
|
|
644 | be defined, in which case memory fences (and similar constructs) are |
|
|
645 | completely removed, leading to more efficient code and fewer dependencies. |
|
|
646 | |
|
|
647 | Setting this symbol to a true value implies C<ECB_NO_SMP>. |
|
|
648 | |
|
|
649 | =item ECB_NO_SMP |
|
|
650 | |
|
|
651 | The weaker version of C<ECB_NO_THREADS> - if F<ecb.h> is used from |
|
|
652 | multiple threads, but never concurrently (e.g. if the system the program |
|
|
653 | runs on has only a single CPU with a single core, no hyperthreading and so |
|
|
654 | on), then this symbol can be defined, leading to more efficient code and |
|
|
655 | fewer dependencies. |
|
|
656 | |
|
|
657 | =back |
|
|
658 | |
|
|
659 | |
