←back to thread

140 points Tomte | 1 comments | | HN request time: 0.202s | source
Show context
fjfaase ◴[] No.26288320[source]
I am working on a tool, which can take a collection of MarkDown files with fragments of C code, and can combine these into a single C file, where all fragments are placed in an order, such that they can be compiled. Because defines can change the meaning of code depending where you place them, there are some restrictions on the input files. An example of the type of input file I have in mind, is given at https://github.com/FransFaase/RawParser/blob/master/docs/gra... . The tool I am developing, and which is far from finished, can be found in https://github.com/FransFaase/IParse in the MarkDownC.cpp file.
replies(2): >>26288829 #>>26290610 #
nerdponx ◴[] No.26290610[source]
This sounds a lot like the R Markdown format. https://rmarkdown.rstudio.com/articles_intro.html
replies(1): >>26293636 #
fjfaase ◴[] No.26293636[source]
I understand that R Markdown format is not similar to the GitHub MarkDown format. (Correct me if I am mistaken.) I would like to use the basis format of GitHub, also because it compatible with the github.io documentation websites.
replies(1): >>26293923 #
1. nerdponx ◴[] No.26293923[source]
I believe it's mostly compatible with Github Markdown and CommonMark. I'm not sure if the code blocks will render properly on Github.