From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: libmdoc.h no longer needs mdoc.h
Date: Thu, 13 Dec 2018 02:30:51 -0500 (EST) [thread overview]
Message-ID: <05f5d180bf0a95b5@fantadrom.bsd.lv> (raw)
Log Message:
-----------
libmdoc.h no longer needs mdoc.h
Modified Files:
--------------
mandoc:
att.c
mandoc_headers.3
Revision Data
-------------
Index: mandoc_headers.3
===================================================================
RCS file: /home/cvs/mandoc/mandoc/mandoc_headers.3,v
retrieving revision 1.24
retrieving revision 1.25
diff -Lmandoc_headers.3 -Lmandoc_headers.3 -u -p -r1.24 -r1.25
--- mandoc_headers.3
+++ mandoc_headers.3
@@ -171,10 +171,6 @@ Common data types for all syntax trees a
can be used everywhere.
.Pp
Requires
-.Qq Pa mandoc_ohash.h
-for
-.Vt struct ohash
-and
.Qq Pa mandoc.h
for
.Vt enum mandoc_os .
@@ -197,6 +193,10 @@ and
.Fn roff_validate .
.Pp
Uses pointers to the types
+.Vt struct ohash
+from
+.Pa mandoc_ohash.h
+and
.Vt struct mdoc_arg
and
.Vt union mdoc_data
@@ -341,11 +341,7 @@ Requires
for
.Vt enum roff_tok
and
-.Qq Pa mdoc.h
-for
-.Vt enum mdoc_*
-and
-.Vt struct mdoc_* .
+.Vt enum roff_sec .
.Pp
Provides
.Vt enum margserr ,
@@ -355,16 +351,16 @@ and many functions internal to the
.Xr mdoc 7
parser.
.Pp
-Uses the opaque type
-.Vt struct mparse
-from
-.Pa read.c .
Uses the types
.Vt struct roff_man
and
.Vt struct roff_node
from
.Pa roff.h
+and
+.Vt struct mdoc_arg
+from
+.Pa mdoc.h
as opaque types for function prototypes.
.Pp
When this header is included, the same file should not include
Index: att.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/att.c,v
retrieving revision 1.16
retrieving revision 1.17
diff -Latt.c -Latt.c -u -p -r1.16 -r1.17
--- att.c
+++ att.c
@@ -21,7 +21,6 @@
#include "mandoc.h"
#include "roff.h"
-#include "mdoc.h"
#include "libmdoc.h"
#define LINE(x, y) \
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2018-12-13 7:30 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=05f5d180bf0a95b5@fantadrom.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).