unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>, emacs-devel@gnu.org
Subject: Re: More (de)compress?
Date: Mon, 19 Aug 2013 18:28:20 +0200	[thread overview]
Message-ID: <m3r4dpprvf.fsf@stories.gnus.org> (raw)
In-Reply-To: <83d2p9lkv4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 19 Aug 2013 19:13:19 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> If you do not intend to bypass jka-compr etc., then I must ask what
> are the use cases for these primitives, and whether they are different
> from those of jka-compr?

If the point is to add more C code just to add more C code just because,
then I don't really see the point.  Are we using bz2/yz decompression in
any performance-critical paths?  Are we compressing even anything in a
performance-critical path?

C code is more segfaulty than Lisp code, so unless we have a good use
case for the C code, I think we should avoid adding more.

-- 
(domestic pets only, the antidote for overdose, milk.)
  No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
  and http://lars.ingebrigtsen.no/2013/08/twenty-years-of-september.html



  reply	other threads:[~2013-08-19 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 12:17 More (de)compress? Dmitry Antipov
2013-08-19 16:13 ` Eli Zaretskii
2013-08-19 16:28   ` Lars Magne Ingebrigtsen [this message]
2013-08-19 16:41 ` Paul Eggert
2013-08-19 16:57   ` Eli Zaretskii
2013-08-20  8:19   ` Dmitry Antipov
2013-08-20 14:32     ` Stefan Monnier
2013-08-20 14:34     ` Stefan Monnier

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=m3r4dpprvf.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=dmantipov@yandex.ru \
    --cc=eliz@gnu.org \
    --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).