Pandoc (Haskell) on Code Deconstructed - Episode 1

jekor walks through the source code of Pandoc to explain how it uses the Parsec library to parse email addresses.

Join me as we look at the source code for the popular Haskell project Pandoc. We'll take it apart, see how it works, and build a program from the components we find. In this, part 1, we'll look at how Pandoc uses the Parsec library to parse email addresses. Links from the video (in order): - vocabulink.com/ (my site that uses the Pandoc library) - jekor.com/ (my personal site that uses the Pandoc command-line program) - whatismarkdown.com/ (Markdown) - en.wikipedia.org/wiki/Ctags (TAGS) - cs.nott.ac.uk/~pszgmh/monparsing.pdf (Monadic Parser Combinators) - github.com/chrisdone/hasktags (hasktags) - github.com/akheron/jansson/blob/master/src/load.c (example C parser for JSON) - github.com/douglascrockford/JSON-js/blob/master/json_parse.j… (example JavaScript parser for JSON) - ietf.org/rfc.html (IETF RFCs) - hackage.haskell.org/package/parsec (Parsec parsing library) My Bash $PS1 is defined as: PS1="\[\033[ 01;37m\]\$(exit=\$?; if [[ \$exit == 0 ]]; then echo \"\[\033[01;32m\]✓\"; else echo \"\[\033[01;31m\]✗ \$exit\"; fi) \[\033[01;32m\]\u\[\033[01;34m\] \W \$\[\033[00m\] " To customize yours, see "Return value visualization" at wiki.archlinux.org/index.php/Color_Bash_Prompt If you use Windows and want to see the exit codes, see stackoverflow.com/questions/334879/how-do-i-get-the-applicat… All Code Deconstructed videos: youtube.com/playlist?list=PLxj9UAX4Em-IBXkvcC3MycLlcxyoi7v8B