[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C and Emacs Lisp code parts
From: |
John Wiegley |
Subject: |
Re: C and Emacs Lisp code parts |
Date: |
Tue, 05 Jul 2016 15:48:50 -0700 |
User-agent: |
Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.95 (darwin) |
>>>>> Eli Zaretskii <address@hidden> writes:
> In which you were asked to provide some numbers, but gave none. Please do
> provide them, and perhaps that bug could be taken care of.
Until we have numbers, no action will be taken here. I am still of the
position that *more* code should be moved from C to Emacs Lisp, and not the
other way around.
If there are cases where this might be a bad idea, measurement is needed to
convince me. As others have said, performance is a complex beast, and human
guesses about how a modern machine operates are more often wrong than not.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
signature.asc
Description: PGP signature
- C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Eli Zaretskii, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Alan Mackenzie, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Eli Zaretskii, 2016/07/01
- Re: C and Emacs Lisp code parts,
John Wiegley <=
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/06
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/06
- Re: C and Emacs Lisp code parts, Phillip Lord, 2016/07/06
- Re: C and Emacs Lisp code parts, John Wiegley, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Eli Zaretskii, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Eli Zaretskii, 2016/07/01
- Re: C and Emacs Lisp code parts, Andy Moreton, 2016/07/01
- Re: C and Emacs Lisp code parts, Karl Fogel, 2016/07/01