From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: #include <stddef.h>, needed for NULL; bug reported by op@
Date: Tue, 21 Jun 2022 05:34:45 -0500 (EST) [thread overview]
Message-ID: <3365cb7869af3d1c@mandoc.bsd.lv> (raw)
Log Message:
-----------
#include <stddef.h>, needed for NULL; bug reported by op@
Modified Files:
--------------
mandoc:
compat_strsep.c
Revision Data
-------------
Index: compat_strsep.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/compat_strsep.c,v
retrieving revision 1.5
retrieving revision 1.6
diff -Lcompat_strsep.c -Lcompat_strsep.c -u -p -r1.5 -r1.6
--- compat_strsep.c
+++ compat_strsep.c
@@ -31,6 +31,8 @@
*/
#include "config.h"
+#include <stddef.h>
+
/*
* Get next token from string *stringp, where tokens are possibly-empty
* strings separated by characters from delim.
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2022-06-21 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3365cb7869af3d1c@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).