tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Unify mdoc and man enums and structs into mandoc.h.
Date: Mon, 04 Oct 2010 08:35:17 +0200	[thread overview]
Message-ID: <4CA975A5.1080104@bsd.lv> (raw)
In-Reply-To: <20101003223647.GA20734@iris.usta.de>

> Many, and conflicting ones; so i cannot present final solutions,
> but some thoughts indeed.

Ingo, yeah, by the large I agree---for the time being I'll revert the 
changes.

> Regarding libmandoc.a, sure.  Actually, i don't see much of a point
> in having libraries at all in this context; i doubt that anybody will
> ever want to use the parsers outside the mandoc program, or, put
> the other way round, all functionality that can reasonably be based
> on the mdoc language can probably reasonably be included into the
> mandoc binary program.
> 
> Regarding makewhatis, apropos and man.cgi, i do not have much hope.
> Remember that those must be able to work on the -Tascii output,
> at least in OpenBSD, because that's the only version of the manuals
> getting installed, and there is next to no hope to have that changed,
> based on what Theo and Bob say.  Besides, i don't really see a need
> to install manual source code either.  On a typical production
> system, you don't need manual source code, just as you don't need
> program source code; besides, the src.tar.gz ball is readily
> available for each release, and anonymous CVS is not rocket science
> either, in case you need the sources for some reason.

I agree, but this is not relevant: if OpenBSD doesn't want to use the 
libraries, the object files can be linked directly into mandoc.

> Regarding mandoc.h, actually, i still don't see the point.
> Why should a file like mdoc_macro.c, or even mdoc_term.c,
> be forced to include man data structures and function prototypes?
> In the current implementation, there is not a single file
> including both man.h and mdoc.h or both libman.h and libmdoc.h,
> except main.c and tree.c.  And even if there were one or two
> such files:  What is the advantage of a frontend file including
> just mandoc.h instead of man.h and mdoc.h?

Yep, this is the reason for my patch reversion.  Pushing libmdoc, 
libman, and libroff tighter together can occur without header merging of 
the {man,mdoc,roff}.h headers.

Kristaps
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-10-04  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201010021014.o92AEcOr023027@krisdoz.my.domain>
     [not found] ` <20101002175621.GB19515@iris.usta.de>
2010-10-03 16:49   ` Kristaps Dzonsons
2010-10-03 22:36     ` Ingo Schwarze
2010-10-04  6:35       ` Kristaps Dzonsons [this message]
2010-10-04 20:05         ` Ingo Schwarze

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=4CA975A5.1080104@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=tech@mdocml.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).