From: Eli Zaretskii <eliz@gnu.org>
To: stephen@xemacs.org
Cc: aurelien.aptel+emacs@gmail.com, dmantipov@yandex.ru,
sdl.web@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Why not zlib-compress-region?
Date: Sat, 28 Jun 2014 20:41:45 +0300 [thread overview]
Message-ID: <83wqc153ty.fsf@gnu.org> (raw)
In-Reply-To: <831tu96kb1.fsf@gnu.org>
> Date: Sat, 28 Jun 2014 20:00:34 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: aurelien.aptel+emacs@gmail.com, dmantipov@yandex.ru, emacs-devel@gnu.org,
> sdl.web@gmail.com, monnier@iro.umontreal.ca
>
> > FFI implementations that *don't* require compilers have their
> > problems, too, since Lisp types sometimes map to different C types for
> > different libraries, which requires a lot of fiddly low-level
> > knowledge on the part of the Lisp programmers that (if they stick to
> > pure Lisp) they just don't need at all. FFI == crashable Lisp.
>
> Something to consider, I'm sure. But that doesn't make the problem of
> having to have a working compiler installation in any way.
The last sentence was meant to say
But that doesn't make the problem of having to have a working
compiler installation go away in any way.
Sorry.
next prev parent reply other threads:[~2014-06-28 17:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 9:20 Why not zlib-compress-region? Leo Liu
2014-06-26 12:07 ` Dmitry Antipov
2014-06-26 13:27 ` Stefan Monnier
2014-06-26 14:03 ` Leo Liu
2014-06-26 16:43 ` Stefan Monnier
2014-06-27 12:50 ` Aurélien Aptel
2014-06-27 13:28 ` Stefan Monnier
2014-06-27 15:32 ` Dmitry Antipov
2014-06-27 22:07 ` Stefan Monnier
2014-06-28 6:50 ` Eli Zaretskii
2014-06-28 12:51 ` Stephen J. Turnbull
2014-06-28 13:16 ` Eli Zaretskii
2014-06-28 16:30 ` Stephen J. Turnbull
2014-06-28 17:00 ` Eli Zaretskii
2014-06-28 17:41 ` Eli Zaretskii [this message]
2014-06-29 3:58 ` Stephen J. Turnbull
2014-06-29 21:03 ` Stefan Monnier
2014-06-28 18:06 ` Paul Eggert
2014-06-28 14:07 ` Richard Stallman
2014-06-27 19:48 ` Ted Zlatanov
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=83wqc153ty.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aurelien.aptel+emacs@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sdl.web@gmail.com \
--cc=stephen@xemacs.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).