[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C and Emacs Lisp code parts
From: |
Eli Zaretskii |
Subject: |
Re: C and Emacs Lisp code parts |
Date: |
Fri, 01 Jul 2016 11:13:51 +0300 |
> From: Andreas Röhler <address@hidden>
> Date: Fri, 1 Jul 2016 10:03:07 +0200
>
> last years parts of C code have been switched into the Lisp area. There
> are pro and cons, the cons seems to be an easier maintenance, to protect
> against the lack of skilled C-developers.
>
> The backside is a general slowness, not felt in details of such a
> change, but cumulated.Would liketo see this strategy changed. Rather
> focus at a fast and small core. Reduce the rate of changes maybe. My
> preferred Emacs must not provide everything, but be quick and reliable
> and easy to extend. Emacs Lisp seen as designed for the user-space.
To compare performance, we need a performance test suite. Without
measuring the impact of these changes, we cannot rationally discuss
the alleged slowdown. This has been discussed before, but AFAIK no
one is working on that.
Volunteers are welcome to work on such a performance test suite. Once
available, we can make it mandatory for the results to be presented
when someone comes with a suggestion to move code from C to Lisp, or
vice versa.
- C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts,
Eli Zaretskii <=
- 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, 2016/07/05
- 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