unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Junpeng Qiu <qjpchmail@gmail.com>
To: emacs-devel@gnu.org, jwiegley@gmail.com
Subject: Re: [ELPA] New package: parsec
Date: Tue, 25 Oct 2016 21:46:57 -0400	[thread overview]
Message-ID: <CAKzohgK5enkqszGF5d13UNMhH_uhfn0sgAaxuLbooJ64tc_5rw@mail.gmail.com> (raw)
In-Reply-To: <m2oa28ayqf.fsf@newartisans.com>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

It is a very interesting idea to combine Free Monad with Parsec. I'll take
a look at it.

>> make it possible for you to compile Haskell-written Parsec parsers into
their corresponding Emacs Lisp "parsec" equivalents

It would be awesome if we can finally do this. For the time being, I'll
mainly working on making parsec more complete, porting more Haskell
functions to Emacs Lisp. It still needs to be more polished to become
really useful.

Thanks for your emacs-pl and the information!

Best,
-Junpeng

On Tue, Oct 25, 2016 at 5:46 PM, John Wiegley <jwiegley@gmail.com> wrote:

> >>>>> "JQ" == Junpeng Qiu <qjpchmail@gmail.com> writes:
>
> JQ> Sorry. I seemed to paste the wrong URL for John's emacs-pl. Here you
> go:
> JQ> [emacs-pl]: https://github.com/jwiegley/emacs-pl
>
> Thanks for the link, Junpeng! In return for your gracious contribution, I
> offer a new Haskell library to play with that you might find useful, since
> it
> should make it possible for you to compile Haskell-written Parsec parsers
> into
> their corresponding Emacs Lisp "parsec" equivalents -- or at least part of
> the
> way. :)
>
>     http://hackage.haskell.org/package/parsec-free
>
> --
> John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
> http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2
>

[-- Attachment #2: Type: text/html, Size: 2251 bytes --]

      reply	other threads:[~2016-10-26  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 20:17 [ELPA] New package: parsec Junpeng Qiu
2016-10-25 20:23 ` Junpeng Qiu
2016-10-25 21:46   ` John Wiegley
2016-10-26  1:46     ` Junpeng Qiu [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=CAKzohgK5enkqszGF5d13UNMhH_uhfn0sgAaxuLbooJ64tc_5rw@mail.gmail.com \
    --to=qjpchmail@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).