From: "Drew Adams" <drew.adams@oracle.com>
To: "'Daniel Colascione'" <daniel@censorshipresearch.org>,
"'Stephen J. Turnbull'" <stephen@xemacs.org>
Cc: 'Chad Brown' <yandros@MIT.EDU>,
'Stefan Monnier' <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: RE: Obsoleting end-user-functions [was: turn-on-* type functions]
Date: Mon, 5 Apr 2010 00:19:17 -0700 [thread overview]
Message-ID: <7B36874B0D264894B3D8954FC67ADADC@us.oracle.com> (raw)
In-Reply-To: <4BB954E9.7050805@censorshipresearch.org>
> > A harder, invasive idea: get rid of explicit byte-compilation,
> > by default.
What do you mean "by default"?
> > If Emacs always byte-compiles out-of-date
> > libraries at load time, the warnings would be generated.
If load implies byte-compile, then, again, what did you mean by "by default"?
When would non-compiled code be used - just by explicit eval (e.g. `C-x C-e')
instead of load?
> 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.
Maybe I'm misunderstanding... Are you suggesting that every load would load
byte-compiled code?
So to use the debugger I would need to explicitly eval stuff (e.g. whole
libraries)? Surely you don't mean for users to debug using byte-compiled code?
next prev parent reply other threads:[~2010-04-05 7:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 1:23 turn-on-bug-reference-mode, turn-on-bug-reference-prog-mode type functions Dan Nicolaescu
2010-04-03 2:00 ` Stefan Monnier
2010-04-03 18:00 ` Richard Stallman
2010-04-03 18:17 ` Davis Herring
2010-04-03 19:43 ` Chad Brown
2010-04-04 14:26 ` Stefan Monnier
2010-04-04 16:19 ` Chad Brown
2010-04-04 18:53 ` Stefan Monnier
2010-04-05 2:29 ` Obsoleting end-user-functions [was: turn-on-* type functions] Stephen J. Turnbull
2010-04-05 3:11 ` Daniel Colascione
2010-04-05 7:19 ` Drew Adams [this message]
2010-04-06 6:41 ` Stephen J. Turnbull
2010-04-05 13:48 ` Obsoleting end-user-functions Stefan Monnier
2010-04-05 14:03 ` Davis Herring
2010-04-05 15:52 ` Chad Brown
2010-04-06 6:48 ` Stephen J. Turnbull
2010-04-07 3:21 ` Richard Stallman
2010-04-04 17:36 ` turn-on-bug-reference-mode, turn-on-bug-reference-prog-mode type functions Richard Stallman
2010-04-03 19:23 ` Dan Nicolaescu
2010-04-03 19:23 ` 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=7B36874B0D264894B3D8954FC67ADADC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=daniel@censorshipresearch.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen@xemacs.org \
--cc=yandros@MIT.EDU \
/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).