Follow-up Comment #9, bug #55107 (project groff): Branden,
[comment #7 comment #7:] > > but troff then incurs the overhead of setting up an IPC pipeline, to capture the preprocessor output, then fork the preprocessor, > > groff already handles all of this. I don't think that it does... > Some of the most important bits are: > > https://git.savannah.gnu.org/cgit/groff.git/tree/src/roff/groff/groff.cpp#n54 > https://git.savannah.gnu.org/cgit/groff.git/tree/src/roff/groff/groff.cpp#n576 > https://git.savannah.gnu.org/cgit/groff.git/tree/src/roff/groff/pipeline.c > > ...or I am badly misunderstanding you. Consider pre-grohtml; that *isn't* run within groff's normal pipeline; it is forked, with its own subsidiary pipeline, as and when required. One of my earliest contributions to groff was to make that subsidiary pipeline setup, and the associated fork, MS-Windows compatible, and I would anticipate a similar overhead, if psbb were to be delegated to a preprocessor. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55107> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
