From: John Wiegley <jwiegley@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andy Sonnenburg <andy22286@gmail.com>, emacs-devel@gnu.org
Subject: Re: Binary Search Tree and Treap Functions bst-assq and treap-put
Date: Mon, 12 Dec 2016 09:06:21 -0800 [thread overview]
Message-ID: <m2y3zl13hu.fsf@newartisans.com> (raw)
In-Reply-To: <jwvshptrsp9.fsf-monnier+Inbox@gnu.org> (Stefan Monnier's message of "Mon, 12 Dec 2016 11:58:31 -0500")
>>>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
SM> You can put a
SM> (eval-when-compile <run-the-C-compiler>)
SM> in the <pkg>.el file, so that the C code gets compiled when the Elisp file
SM> is byte-compiled.
Except that <run-the-C-compiler> may vary greatly, depending on platform and
dependencies. How "universal" does an entry in ELPA need to be? How many
platforms should it build for?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-12-12 17:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 1:42 Binary Search Tree and Treap Functions bst-assq and treap-put Andy Sonnenburg
2016-12-04 4:33 ` Stefan Monnier
[not found] ` <CAHtDYY-xis2R4Nbvq_8Ht0nKsm6KjGqW=NSC7O3+5FvNF9w+Dg@mail.gmail.com>
[not found] ` <CAHtDYY9__BVOAs+vX=Tj8Bf31X6-Duv3f9MS8vcGwsnO2x74+w@mail.gmail.com>
2016-12-04 12:14 ` Andy Sonnenburg
2016-12-04 17:04 ` Stefan Monnier
2016-12-04 17:13 ` Andy Sonnenburg
2016-12-04 17:39 ` Andy Sonnenburg
2016-12-04 17:41 ` Eli Zaretskii
2016-12-12 6:15 ` John Wiegley
2016-12-12 12:56 ` Stefan Monnier
2016-12-12 16:46 ` John Wiegley
2016-12-12 16:58 ` Stefan Monnier
2016-12-12 17:06 ` John Wiegley [this message]
2016-12-12 17:29 ` Stefan Monnier
2017-10-22 16:35 ` Noam Postavsky
2017-10-22 16:44 ` Andreas Schwab
2017-10-22 16:44 ` Stefan Monnier
2017-10-22 17:12 ` Noam Postavsky
2017-10-23 0:37 ` 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=m2y3zl13hu.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=andy22286@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).