From: Hans-Bernhard B. <br...@ph...> - 2004-05-27 12:16:54
|
On Wed, 26 May 2004, Ethan Merritt wrote: > 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 Nah, that's terminally ugly. ;-) If the change to 'int' for K&R can work (needs a bit of testing), then the same 'int' will work for ANSI C, too. So making this distinction would serve no useful purpose. -- Hans-Bernhard Broeker (br...@ph...) Even if all the snow were burnt, ashes would remain. |