Files
mercury/samples/c_interface
Tyson Dowd d64781a3d7 Add a testing architecture for the samples directory.
Estimated hours taken: 15

Add a testing architecture for the samples directory.
The tests are in the "tests" subdirectory of the samples
directory.  This keeps them close to the samples, but not close
enough to clutter up the samples.
It also means you don't have to worry about the issue of exactly where
the developer has checked out the CVS tests module.

samples/c_interface/simpler_c_calls_mercury/Mmakefile:
	Update this example to generate a .a file
	instead of directly using $(mercury_lib.os)

samples/tests/*:
	Test cases for all the samples.
2000-02-14 05:28:45 +00:00
..

This directory contains some examples of mixed Mercury/C programs using
the C interface.

short_example.m                 A short example of Mercury code calling C.

mercury_calls_c                 A detailed example of Mercury code
                                calling C code.

c_calls_mercury                 A detailed example of C code calling
                                Mercury code.

mercury_calls_cplusplus         A detailed example of Mercury code
                                calling C++ code.

cplusplus_calls_mercury         A detailed example of C++ code calling
                                Mercury code.

mercury_calls_fortran           This directory contains a detailed
                                example of Mercury code calling Fortran code.

simpler_c_calls_mercury         A simpler example of C code calling Mercury.

simpler_cplusplus_calls_mercury A simpler example of C++ code calling
                                Mercury.