all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: Why are the tests byte-compiled
Date: Fri, 17 Jun 2016 16:25:49 +0100	[thread overview]
Message-ID: <871t3v25xe.fsf@russet.org.uk> (raw)
In-Reply-To: <580a842e-d2f3-49c1-80f7-0dd78d04870a@default> (Drew Adams's message of "Fri, 17 Jun 2016 08:13:25 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

>> >> Conclusion: the emacs tests should not be byte-compiled.
>> >> Or am I missing something?
>> >
>> > Backtraces include byte-code for code that was compiled.  They
>> > should not.  Rather, it should at least be possible for a user
>> > or a program to elide the byte-code in a backtrace.
>> 
>> Sure, but in this case the byte-code hides everything of use.
>> I can't see any reason *why* they are byte compiled.
>
> Yes, sorry if I was not clear.  There are two things that could
> be improved:
>
> 1. The issue you raised, which is whether or not test code should
>    be byte-compiled.


I'll try turning it off and see what happens! Seems to be the quickest
way to find the answer.

Phil



  reply	other threads:[~2016-06-17 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 20:23 Why are the tests byte-compiled Phillip Lord
2016-06-15 21:55 ` Drew Adams
2016-06-17 15:02   ` Phillip Lord
2016-06-17 15:13     ` Drew Adams
2016-06-17 15:25       ` Phillip Lord [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-26  5:18 Noam Postavsky
2016-06-27 13:35 ` Phillip Lord

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t3v25xe.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.