From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: lekktu@gmail.com, stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: Location of tests (again) (was Re: Makefile-help)
Date: Sat, 07 Nov 2015 13:45:52 +0200 [thread overview]
Message-ID: <83twoyowwf.fsf@gnu.org> (raw)
In-Reply-To: <87k2pucaw3.fsf@russet.org.uk>
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Sat, 07 Nov 2015 11:22:04 +0000
> Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
> Emacs developers <emacs-devel@gnu.org>
>
> Juanma Barranquero <lekktu@gmail.com> writes:
>
> > On Sat, Nov 7, 2015 at 11:55 AM, Phillip Lord <phillip.lord@russet.org.uk>
> > wrote:
> >
> >> Some one suggested to
> >> but tests of C core ~test/automated/src~ which sounded good. But
> >> thinking about it, it probably makes more sense to leave this for C
> >> level testing framework. So now we have
> >>
> >> test/automated/lisp
> >> test/automated/lisp/emacs-lisp
> >> test/automated/lisp/progmodes (and so on....)
> >> test/automated/lisp/c (lisp tests for the C core)
> >
> > This breaks the symmetry between our source layout and the test layout.
>
> It does, and I think this is unfortunate.
Sorry, I don't understand why not use the simpler
test/automated/src (tests for the C core)
test/automated/lisp
test/automated/lisp/emacs-lisp
...
> > In fact, it seems to me like a nice property that if we have both C and
> > elisp tests for, say, keymap.c, then keymap-tests.c and keymap-tests.el are
> > in close proximity.
>
> I thought about that. Obviously it makes the Makefile harder (since you
> need one that can cope with both the C framework and the Lisp
> framework), which is why I though to keep things separate. This seemed
> worth breaking the symmetry.
We don't have any C framework, and I very much doubt we will any time
soon. (I don't even think it's feasible, since Emacs is not a
library, and doesn't provide a way of exercising it from a C program.)
We can move files again if and when we do, just like we intend to move
files now. OTOH, breaking the symmetry on behalf of a feature we
don't have doesn't sound right to me.
next prev parent reply other threads:[~2015-11-07 11:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 17:36 Locations of Tests Phillip Lord
2015-11-04 17:53 ` John Wiegley
2015-11-04 18:14 ` Artur Malabarba
2015-11-04 18:21 ` John Wiegley
2015-11-25 9:23 ` Phillip Lord
2015-11-25 9:43 ` Artur Malabarba
2015-11-25 14:17 ` Phillip Lord
2015-11-04 19:15 ` Steinar Bang
2015-11-04 19:23 ` David Kastrup
2015-11-04 21:33 ` Phillip Lord
2015-11-04 19:07 ` Michael Albinus
2015-11-04 19:15 ` John Wiegley
2015-11-04 21:26 ` Phillip Lord
2015-11-05 13:41 ` Stephen Leake
2015-11-05 13:59 ` Artur Malabarba
2015-11-05 15:02 ` Nicolas Petton
2015-11-05 15:08 ` Artur Malabarba
2015-11-06 9:56 ` Phillip Lord
2015-11-05 15:27 ` Juanma Barranquero
2015-11-06 9:55 ` Phillip Lord
2015-11-06 10:02 ` Makefile-help (was Re: Locations of Tests) Phillip Lord
2015-11-07 6:48 ` Stephen Leake
2015-11-07 10:55 ` Location of tests (again) (was Re: Makefile-help) Phillip Lord
2015-11-07 11:06 ` Juanma Barranquero
2015-11-07 11:22 ` Phillip Lord
2015-11-07 11:36 ` Juanma Barranquero
2015-11-07 17:46 ` Phillip Lord
2015-11-07 11:45 ` Eli Zaretskii [this message]
2015-11-07 18:09 ` Stephen Leake
2015-11-10 20:34 ` Przemysław Wojnowski
2015-11-10 20:45 ` Phillip Lord
2015-11-10 21:41 ` Przemysław Wojnowski
2015-11-10 22:27 ` John Wiegley
2015-11-11 0:28 ` bikeshedding (was Re: Location of tests (again) (was Re: Makefile-help)) Stephen Leake
2015-11-11 10:31 ` Location of tests (again) (was Re: Makefile-help) Phillip Lord
2015-11-11 17:02 ` UI tests Richard Stallman
2015-11-11 17:25 ` John Wiegley
2015-11-12 14:09 ` Phillip Lord
2015-11-12 14:37 ` Alan Mackenzie
2015-11-12 16:33 ` Eli Zaretskii
2015-11-13 21:58 ` Richard Stallman
2015-11-15 12:14 ` Przemysław Wojnowski
2015-11-16 19:32 ` Richard Stallman
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=83twoyowwf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=phillip.lord@russet.org.uk \
--cc=stephen_leake@stephe-leake.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.