Skip to content

Commit

Permalink
Markdown with @cond and @endcond
Browse files Browse the repository at this point in the history
In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.).
Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added.
  • Loading branch information
albert-github authored and Dimitri van Heesch committed Nov 22, 2015
1 parent 8504fc3 commit c5a7911
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions src/commentcnv.l
Expand Up @@ -781,6 +781,7 @@ void replaceComment(int offset);
//printf("** Adding start of comment!\n");
if (g_lang!=SrcLangExt_Python &&
g_lang!=SrcLangExt_VHDL &&
g_lang!=SrcLangExt_Markdown &&
g_lang!=SrcLangExt_Fortran)
{
ADDCHAR('/');
Expand All @@ -800,6 +801,7 @@ void replaceComment(int offset);
{
if (g_lang!=SrcLangExt_Python &&
g_lang!=SrcLangExt_VHDL &&
g_lang!=SrcLangExt_Markdown &&
g_lang!=SrcLangExt_Fortran)
{
ADDCHAR('*');
Expand Down

0 comments on commit c5a7911

Please sign in to comment.