[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why are the tests byte-compiled
From: |
Phillip Lord |
Subject: |
Re: Why are the tests byte-compiled |
Date: |
Fri, 17 Jun 2016 16:02:53 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) |
Drew Adams <address@hidden> writes:
>> I'm just trying to write some tests, and I get an error like this.
>>
>> Test open-this-file backtrace:
>> #[nil "\306\307!\310\311\216\n\312P\313\314!\315\216\316\314\310
>> ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
>>
>> Which is pretty useless for debugging. On the other hand, if I launch
>> the erts using the same command as the makefile uses but directly on the
>> source file (i.e. not byte compiled) then I get.
>>
>> Test open-this-file backtrace:
>> (let ((file (concat vc-git-tests-data-dir "file1.txt")) (git-dir (ge
>> (setq value-0 (let ((file (concat vc-git-tests-data-dir "file1.txt")
>>
>> which is useful.
>>
>> 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.
Phil