From: Ethan M. <merritt@u.washington.edu> - 2004-05-26 17:59:35
|
On Wednesday 26 May 2004 10:03 am, Hans-Bernhard Broeker wrote: > On Wed, 26 May 2004, Ethan Merritt wrote: > > But what does that mean in terms of handling the current problem? > > It means that we revert Petr's patch iff we decide to go ANSI C now, or > extend it if we want to stick with K&R compatibility. How about if we define a new type in gp_types.h #undef CHAROUT #ifdef KR /* I don't know what the proper test is for K&R */ #typedef int CHAROUT #else #typedef char CHAROUT #endif and then change all the enhanced text function with a char argument to have a CHAROUT argument instead. That reduces the chance of breaking compilation on platforms for which the existing code works, and still allows us to accommodate K&R's dislike of char arguments. e.g. static void do_enh_writec __PROTO((CHAROUT c)); -- Ethan A Merritt merritt@u.washington.edu Biomolecular Structure Center Mailstop 357742 University of Washington, Seattle, WA 98195 |