… | |
… | |
14 | TODO: document portability requirements for atomic pointer access |
14 | TODO: document portability requirements for atomic pointer access |
15 | TODO: possible cb aliasing? |
15 | TODO: possible cb aliasing? |
16 | TODO: document requirements for function pointers and calling conventions. |
16 | TODO: document requirements for function pointers and calling conventions. |
17 | |
17 | |
18 | - ev.h wasn't valid C++ anymore, which tripped compilers other than |
18 | - ev.h wasn't valid C++ anymore, which tripped compilers other than |
19 | clang, msvc or gcc (analyzed by Raphael 'kena' Poss). |
19 | clang, msvc or gcc (analyzed by Raphael 'kena' Poss). Unfortunately, |
|
|
20 | C++ doesn't support typedefs for function pointers fully, so the affected |
|
|
21 | declarations have to spell out the types each time. |
20 | - when not using autoconf, tighten the check for clock_gettime and related |
22 | - when not using autoconf, tighten the check for clock_gettime and related |
21 | functionality. |
23 | functionality. |
22 | |
24 | |
23 | 4.18 Fri Sep 5 17:55:26 CEST 2014 |
25 | 4.18 Fri Sep 5 17:55:26 CEST 2014 |
24 | - events on files were not always generated properly with the |
26 | - events on files were not always generated properly with the |