Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 4991:97c45e3ad810
implement configure test for whether ndbm.h prototypes are broken
-------------------- ChangeLog entries follow: --------------------
ChangeLog addition:
2010-02-06 Ben Wing <ben@xemacs.org>
* configure:
* configure.ac (AC_LANG):
* configure.ac (TAB):
Add AC_LANG(C++) defs in a way very similar to AC_LANG(C), inserting
our own flags, compiler, etc.
When using g++, if we found ndbm, check whether we can compile a
file using g++ and ndbm.h, calling some DBM routines. Currently, this
fails because the prototypes in ndbm.h are incomplete, omitting the
arguments, which doesn't work with g++. When ndbm.h is bad, we don't
include it and instead provide our own prototypes; otherwise, we
define TRUST_NDBM_H_PROTOTYPES, which signals to use the ones in
ndbm.h.
src/ChangeLog addition:
2010-02-06 Ben Wing <ben@xemacs.org>
* config.h.in: Add undef for TRUST_NDBM_H_PROTOTYPES.
* database.c:
* database.c (struct):
Use TRUST_NDBM_H_PROTOTYPES to determine whether to include ndbm.h
or to specify our own prototypes, in place of CYGWIN_HEADERS (or
more generally, any random list of systems).
* depend: Regenerate.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Sat, 06 Feb 2010 03:26:34 -0600 |
parents | 74fd4e045ea6 |
children |
rev | line source |
---|---|
398 | 1 This directory contains XEmacs' automated test suite. The usual way |
2 of running all the tests is running `make check' from the top-level | |
3 source directory. | |
4 | |
5 The test suite is unfinished and it's still lacking some essential | |
6 features. It is nevertheless recommended that you run the tests to | |
7 confirm that XEmacs behaves correctly. | |
8 | |
9 If you want to run a specific test case, you can do it from the | |
10 command-line like this: | |
11 | |
12 $ xemacs -batch -l test-harness.elc -f batch-test-emacs TEST-FILE | |
13 | |
14 If something goes wrong, you can run the test suite interactively by | |
15 loading `test-harness.el' into a running XEmacs and typing | |
16 `M-x test-emacs-test-file RET <filename> RET'. You will see a log of | |
17 passed and failed tests, which should allow you to investigate the | |
18 source of the error and ultimately fix the bug. | |
19 | |
20 Adding a new test file is trivial: just create a new file here and it | |
21 will be run. There is no need to byte-compile any of the files in | |
22 this directory -- the test-harness will take care of any necessary | |
23 byte-compilation. | |
24 | |
25 Look at the existing test cases for the examples of coding test cases. | |
26 It all boils down to your imagination and judicious use of the macros | |
27 `Assert', `Check-Error', `Check-Error-Message', and `Check-Message'. |