Tom, This is a good list below, but I suggest we wrap them in the generated config header where the build system takes care of the declaration automatically. It'd be content either in the brlcad_config.h header or in some brlcad_compat.h header that (probably) common.h would include. It'd contain blocks like this:
#if defined(HAVE_FEATURE) && !defined(HAVE_DECL_FEATURE) int feature(); #endif Which would solely exist to declare the interface/type/feature/whatever when it's available, but has been disabled due to compilation settings. Some would be more complex, but it's the gist. Cheers! Sean On Sep 28, 2013, at 7:55 AM, [email protected] wrote: > Revision: 57936 > http://sourceforge.net/p/brlcad/code/57936 > Author: tbrowder2 > Date: 2013-09-28 11:55:08 +0000 (Sat, 28 Sep 2013) > Log Message: > ----------- > add files for strict C89 compliance > > Added Paths: > ----------- > brlcad/trunk/src/compat/README > brlcad/trunk/src/compat/README.compat > brlcad/trunk/src/compat/fdopen_compat.h > brlcad/trunk/src/compat/fileno_compat.h > brlcad/trunk/src/compat/gethostname_compat.h > brlcad/trunk/src/compat/posix_memalign_compat.h > brlcad/trunk/src/compat/realpath_compat.h > brlcad/trunk/src/compat/snprintf_compat.h > brlcad/trunk/src/compat/strcasecmp_compat.h > brlcad/trunk/src/compat/strncasecmp_compat.h ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
