From: Artur Malabarba <bruce.connor.am@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Proposed new core library: pl.el
Date: Sun, 08 Nov 2015 22:31:38 +0000 [thread overview]
Message-ID: <87611cnmwl.fsf@gmail.com> (raw)
In-Reply-To: <87r3k0us8h.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 08 Nov 2015 15:54:38 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Artur, since there have been no further comments, maybe it would help if
> I explained why I'm not convinced: because parsing libraries tend to be
> very performance-sensitive and could take advantage of the core in ways
> that most other libraries don't. They are also rare, so it makes sense
> to treat them with special care instead of as just another library.
Yes, this makes sense.
My comment was more about dependency libs in general, not really about parsing libs.
> The only other example I know is SMIE, which again lives in the core.
> So there are two things that would convince me in combination:
>
> 1) examples of other parsing libraries in ELPAs (GNU or otherwise)
That I'm aware there's edn.el: https://github.com/expez/edn.el
> 2) examples of packages that would use PL *and* want to support Emacs 24
> or older (please, let's not invent them, I want actual examples)
The only examples that come to mind are the ones I was involved in.
ham-mode and SX (both from Melpa) both manually parse html and would
benefit from a lib for that. (Am I correct in understanding pl helps
with html parsing?)
I'd be fine with dropping 24 support on ham-mode because it's rather
niche, but I wouldn't to drop it on SX (but then, I'm not even sure I'd
use `pl' on SX because its needs are very specific and fine-tuned).
Anyway, you've convinced me that this lib might be good in core. So I'm
OK with this now.
next prev parent reply other threads:[~2015-11-08 22:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 2:14 Proposed new core library: pl.el John Wiegley
2015-11-05 2:22 ` Dmitry Gutov
2015-11-05 2:41 ` ELPA policy (was: Proposed new core library: pl.el) John Wiegley
2015-11-05 3:00 ` ELPA policy Dmitry Gutov
2015-11-05 9:08 ` Artur Malabarba
2015-11-05 12:51 ` Michael Welsh Duggan
2015-11-05 13:49 ` Dmitry Gutov
2015-11-05 14:41 ` Michael Welsh Duggan
2015-11-05 15:09 ` John Wiegley
2015-11-05 15:40 ` Dmitry Gutov
2015-11-05 16:58 ` Artur Malabarba
2015-11-05 17:45 ` Dmitry Gutov
2015-11-06 21:37 ` Richard Stallman
2015-11-08 16:30 ` John Wiegley
2015-11-08 17:11 ` Eli Zaretskii
2015-11-08 18:00 ` Wolfgang Jenkner
2015-11-08 18:20 ` Eli Zaretskii
2015-11-09 0:53 ` Wolfgang Jenkner
2015-11-08 18:26 ` Óscar Fuentes
2015-11-08 18:31 ` Eli Zaretskii
2015-11-08 19:27 ` Artur Malabarba
2015-11-08 18:33 ` Eli Zaretskii
2015-11-08 20:04 ` Artur Malabarba
2015-11-08 19:58 ` Eli Zaretskii
2015-11-08 20:10 ` Dmitry Gutov
2015-11-08 20:26 ` Eli Zaretskii
2015-11-08 20:36 ` Dmitry Gutov
2015-11-08 20:47 ` Eli Zaretskii
2015-11-08 23:16 ` Richard Stallman
2015-11-09 1:45 ` Dmitry Gutov
2015-11-09 2:59 ` Yuri Khan
2015-11-08 19:55 ` Artur Malabarba
2015-11-09 9:25 ` Stephen Leake
2015-11-05 7:13 ` David Kastrup
2015-11-05 9:19 ` Proposed new core library: pl.el Artur Malabarba
2015-11-05 20:19 ` Ted Zlatanov
2015-11-05 23:54 ` Artur Malabarba
2015-11-06 15:35 ` Ted Zlatanov
2015-11-08 20:54 ` Ted Zlatanov
2015-11-08 22:31 ` Artur Malabarba [this message]
2015-11-09 22:02 ` John Wiegley
2015-11-09 23:14 ` Artur Malabarba
2015-11-09 23:18 ` John Wiegley
2015-11-10 1:45 ` Ted Zlatanov
2015-11-11 14:51 ` Ted Zlatanov
2015-11-11 15:08 ` Nicolas Petton
2015-11-11 15:28 ` Ted Zlatanov
2015-11-11 17:27 ` Artur Malabarba
2015-11-11 17:38 ` Artur Malabarba
2015-11-11 18:38 ` Ted Zlatanov
2015-11-11 17:03 ` Richard Stallman
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=87611cnmwl.fsf@gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.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.
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).