[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Obsoleting end-user-functions [was: turn-on-* type functions]

From: Daniel Colascione
Subject: Re: Obsoleting end-user-functions [was: turn-on-* type functions]
Date: Sun, 04 Apr 2010 23:11:37 -0400
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100317 Thunderbird/3.0.4

Hash: SHA1

On 4/4/10 10:29 PM, Stephen J. Turnbull wrote:
> Stefan Monnier writes:
> A harder, invasive idea: get rid of explicit byte-compilation, by
> default.  If Emacs always byte-compiles out-of-date libraries at load
> time, the warnings would be generated.

I've been using byte-code-cache.el for years. It reimplements load in
lisp, byte-compiling files and automatically caching the results. It's a
hack, but it works very well for most things I try with it; to date, the
only things I've seen break with it are tramp and nxhtml, though I
haven't put as much effort as I should have into figuring out _why_ it

> Rationale: I don't think I've ever seen a test-suite difference
> between byte-compiled and directly interpreted code in XEmacs, and
> only a few such bugs in beta testing or end use.  Of course in the
> nature of Lisp there may need to be a way to inhibit byte compilation,
> but these days I think it's appropriate to require a flag of some kind
> (command-line option, Lisp variable) to inhibit.

For a long time, SBCL got by very well without an interpreter. It only
recently grew one to deal with some special cases.
Version: GnuPG v1.4.10 (Darwin)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]