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

[Daniel Colascione <daniel@censorshipresearch.org>]

-----BEGIN PGP SIGNED MESSAGE-----
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
breaks.

> 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEARECAAYFAku5VOkACgkQ17c2LVA10VsNfwCgw6MjjlGEINjgD1hXwbdm6T20
SrYAoKseLJYmlEnof5IJuE3jOh2LJ0KM
=paP/
-----END PGP SIGNATURE-----