From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: improve a comment explaining a particularly nasty hack; no code
Date: Thu, 19 May 2022 09:49:26 -0500 (EST) [thread overview]
Message-ID: <33653350361650b5@mandoc.bsd.lv> (raw)
Log Message:
-----------
improve a comment explaining a particularly nasty hack; no code change
Modified Files:
--------------
mandoc:
read.c
Revision Data
-------------
Index: read.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/read.c,v
retrieving revision 1.220
retrieving revision 1.221
diff -Lread.c -Lread.c -u -p -r1.220 -r1.221
--- read.c
+++ read.c
@@ -261,7 +261,12 @@ mparse_buf_r(struct mparse *curp, struct
lastln = thisln;
}
- /* XXX Ugly hack to mark the end of the input. */
+ /*
+ * XXX Ugly hack to mark the end of the input,
+ * such that the function roff_parse_comment()
+ * doesn't attempt to append another line if the
+ * last input line ends with an escape character.
+ */
if (i == blk.sz || blk.buf[i] == '\0') {
if (pos + 2 > ln.sz)
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2022-05-19 14:49 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=33653350361650b5@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).