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