public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Why cmark is written in C?
Date: Sun, 6 Aug 2017 08:37:38 -0700	[thread overview]
Message-ID: <20170806153738.GC78163@Johns-MBP> (raw)
In-Reply-To: <89ae88db-f9be-499c-b743-fe2d2cbc5ee7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

1. Speed.
2. Portability (easy to create bindings to a C library in
   any other language).
3. The current parsing algorithm is imperative in style;
   the C library gives a model that can easily be copied
   in other imperative languages.

+++ Kolen Cheung [Aug 05 17 21:33 ]:
>Hi, I'm just curious. Why cmark is written in C instead of Haskell?
>
>(A longer but more accurate question should be why write it in C and provide a Haskell binding and not the other way around?)
>
>-- 
>You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/89ae88db-f9be-499c-b743-fe2d2cbc5ee7%40googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2017-08-06 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06  4:33 Kolen Cheung
     [not found] ` <89ae88db-f9be-499c-b743-fe2d2cbc5ee7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 15:37   ` John MacFarlane [this message]
2017-08-06 15:38   ` John MacFarlane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170806153738.GC78163@Johns-MBP \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).