Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Do not enforce POSIX if __STRICT_ANSI__ is defined
On b4c1548 I proposed defining _POSIX_C_SOURCE in order to enable the macros to use POSIX under unix-like systems, as POSIX was used anyway. Here I propose to follow whatever the user wants. This means: - If the user explicitly defines a strict standard C compliance (e.g. compiling using `--std=c99`) then we do not use any POSIX feature. This is detected through the definition of the __STRICT_ANSI__ macro. - If the user does not enforce any C standard, we assume POSIX is available as before if the system is unix-like. I believe this approach is better than the previous one because if any cutest user does not want to rely on POSIX features we do not force it. However by default we use them if they are available.
- Loading branch information