From 1a9e227917248d449b7dee394c1cba081bc249be Mon Sep 17 00:00:00 2001 From: Yuqian Yang Date: Wed, 5 Mar 2025 00:21:48 +0800 Subject: feat(www): add post systemd-nspawn. --- www/content/posts/c-func-ext.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 www/content/posts/c-func-ext.md (limited to 'www/content/posts/c-func-ext.md') diff --git a/www/content/posts/c-func-ext.md b/www/content/posts/c-func-ext.md new file mode 100644 index 0000000..f5ab8fb --- /dev/null +++ b/www/content/posts/c-func-ext.md @@ -0,0 +1,23 @@ +--- +title: "Libc/POSIX Function \"Extensions\"" +date: 2025-03-04T13:40:33+08:00 +lastmod: 2025-03-04T13:40:33+08:00 +categories: coding +tags: + - c + - posix +--- + +Recently, I've been working on porting libraries to GNU/Hurd. The maintainers of GNU/Hurd +have a strong belief that [`*_MAX` macros on POSIX system interfaces](https://pubs.opengroup.org/onlinepubs/9699919799.2008edition/nframe.html) +are very evil things. This is indeed true as a lot of (old) libraries relying on those macros +to determine the buffer size. In modern programming world, it is definitely a bad +idea to use fixed values for buffer sizes without considering possible overflow, unless +you are certain that size is sufficient. + +When you get rid of some old things, you will always meet compatibility problems. In these +case, old source codes using these macros just do not compile now. So here are some + + + + -- cgit v1.2.3