diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2025-01-02 15:59:57 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2025-01-02 15:59:57 +0100 |
| commit | 53bce88c52c3c6dba3ab4d1d9abf2036de051fe8 (patch) | |
| tree | 0cb344068524b1485a09ffeaf193f40e7e68a363 | |
| parent | 4ddd662b3c206eb6737d78f8c51e687a33db7cfa (diff) | |
typo
| -rw-r--r-- | faq/foo_max.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/faq/foo_max.mdwn b/faq/foo_max.mdwn index 14015b9b..5f736680 100644 --- a/faq/foo_max.mdwn +++ b/faq/foo_max.mdwn @@ -39,7 +39,7 @@ since Posix 2008 `realpath(path, NULL)` and `getcwd(NULL, 0)` allocate the path dynamically. In general, using `FOO_MAX` in source code (with a large value) leads to code -that is not acually checking against overflows. `PATH_MAX` being 4096 is +that is not actually checking against overflows. `PATH_MAX` being 4096 is actually "wrong" on Linux: $ printf '#include <limits.h>\nPATH_MAX' | cpp -P |