All universal programming languages (assembler, C, CLIP, Lisp, Cobol, Python, Java) can parse perl as well.
Only if they implement Perl, perfectly mimicking the functionality of perl (the only spec for Perl). Amongst other difficulties, Perl has available the full power of Perl at the preprocessing stage.
But then these “most implementations” are not implementations of “standard Markdown,”
Note the qualifier—“most implementations that work with client data”. Markdown is also used extensively to generate static content that is not user-generated.
There are still multiple implementations used in generating static content, no two of which really do the same thing, e.g., pandoc, multimarkdown, and etc. These are all still arguably “markdown” (at least, they call themselves that) but don’t conform to standard markdown as you understand it.
Oh, I see—a specification in the style of “only perl can parse perl.”
But then these “most implementations” are not implementations of “standard Markdown,” hence my confusion.
All universal programming languages (assembler, C, CLIP, Lisp, Cobol, Python, Java) can parse perl as well.
Only if they implement Perl, perfectly mimicking the functionality of
perl(the only spec for Perl). Amongst other difficulties, Perl has available the full power of Perl at the preprocessing stage.That doesn’t matter, kind of like non-paperclips.
Note the qualifier—“most implementations that work with client data”. Markdown is also used extensively to generate static content that is not user-generated.
There are still multiple implementations used in generating static content, no two of which really do the same thing, e.g., pandoc, multimarkdown, and etc. These are all still arguably “markdown” (at least, they call themselves that) but don’t conform to standard markdown as you understand it.