Re: build customizability

[Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>]

On 5/4/20 2:45 AM, brainchild wrote:
> *Markdown reader dependencies: *I now understand the conflict. In many 
> potential deployment scenarios, for example applications that employ 
> Markdown source, the embedding of snippets in some target language is 
> unlikely to be needed, except perhaps as narrowly allowed for equations. 
> Thus, if this functionality were entirely enclosed in extensions, and if 
> those extensions could be disabled in the build, then in principle it 
> may be possible to realize the benefit of removing the dependencies on 
> the parsers. I understand that it would require restructuring the code.

Just replying to this - in this case, you're getting far removed from 
Pandoc's processing, to the point where the input file for Pandoc is no 
longer compatible with your system.  What - at this point - is the 
benefit for using the Pandoc codebase?  If all you want is to parse 
Markdown or Latex or some other input format, there's lots of 
specialized parsers out there.

And further than that - what is the benefit to *Pandoc* of you using the 
Pandoc code base?  Since this would require a large restructure of the 
core code, what makes that restructure worthwhile to the Pandoc project? 
  Again, you're getting well off of Pandoc's goals and aim - and there 
are other products that do aim for that use.

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------