Re: mdocml: Unify mdoc and man enums and structs into mandoc.h.

[Kristaps Dzonsons <kristaps@bsd.lv>]

>> Log Message:
>> -----------
>> Unify mdoc and man enums and structs into mandoc.h.
>> This is part of the slow process of logically splitting
>> formatting frontend and parser backend without pollution.
> 
> Hmm, i fear i don't understand this.
> Given the relation "depends on" shown as "<-",
> i would expect the following dependencies:
> 
>   frontends (html.h, term.h)    <- general & output utils
>   backends (*man.h, *mdoc.h)    <- general utils
>   preprocessor (roff.h)         <- general utils
>   output utils (chars.h, out.h) <- none
>   general utils (*mandoc.h)     <- none
> 
> But i don't understand why two different frontends or two
> different backends should depend on each other, or why including
> one might make it necessary to include the other.
> 
> Sorry, i'm lacking the tiome right now to look deeper into this...

Ingo, cross-posting to tech@....

I want to make a simple mandoc.h and libmandoc.a that has all the 
ingredients for writing front-ends, such as a fancier makewhatis and 
apropos, or man.cgi or whatnot.

To begin with: roff.h, mdoc.h, and man.h -> mandoc.h; libmdoc.a, 
libroff.a, and libman.a (and associated stuff) being merged into a 
single libmandoc.a.  Then libmdoc.h, libman.h, and libroff.h being 
merged into libmandoc.h, used internally within libmandoc.a.

This will reduce structural complexity that's been bothering me for a while.

Once this is done, I will abstract and push the fdesc() function into 
the library: it implements parts of the grammar (such as escaped 
newlines) that should be internal to the library.

Another push is to get the escape routines in one place; right now, the 
functionality is duplicated.  Restructuring is a necessary precondition 
before I do so.

Thoughts?

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