mirror of
https://github.com/MariaDB/server.git
synced 2025-01-20 14:02:32 +01:00
d1fb292251
my_atomic_XX_t -> intXX, no implicit locking anymore simplified framework, support for requested cleanups dbug/dbug.c: compiler warning include/atomic/nolock.h: my_atomic_XX_t -> intXX include/atomic/rwlock.h: my_atomic_XX_t -> intXX, no implicit locking anymore include/atomic/x86-gcc.h: my_atomic_XX_t -> intXX, no implicit locking anymore include/atomic/x86-msvc.h: my_atomic_XX_t -> intXX simplified defines support for cleanups include/my_atomic.h: my_atomic_XX_t -> intXX, no implicit locking anymore simplified framework, support for requested cleanups unittest/examples/no_plan-t.c: compiler warning unittest/mysys/Makefile.am: fix for dependencies unittest/mysys/my_atomic-t.c: my_atomic_XX_t -> intXX, no implicit locking anymore unittest/mytap/tap.c: cosmetic fix
21 lines
511 B
C
21 lines
511 B
C
|
|
#include "my_config.h"
|
|
|
|
#include <stdlib.h>
|
|
#include <tap.h>
|
|
|
|
/*
|
|
Sometimes, the number of tests is not known beforehand. In those
|
|
cases, the plan can be omitted and will instead be written at the
|
|
end of the test (inside exit_status()).
|
|
|
|
Use this sparingly, it is a last resort: planning how many tests you
|
|
are going to run will help you catch that offending case when some
|
|
tests are skipped for an unknown reason.
|
|
*/
|
|
int main() {
|
|
ok(1, " ");
|
|
ok(1, " ");
|
|
ok(1, " ");
|
|
return exit_status();
|
|
}
|