|
From: | Nikos Chantziaras |
Subject: | Re: [Lynx-dev] [Patch] Lynx won't compile against zlib 1.2.5.1 |
Date: | Mon, 19 Sep 2011 04:28:37 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110822 Thunderbird/6.0 |
On 09/19/2011 04:13 AM, Thomas Dickey wrote:
On Sun, 18 Sep 2011, Keith Bowes wrote:Je 2011-Sep-17 je 08:09, Thomas Dickey skribis:ON/OFF are on the other hand unnecessary in lynx altogether - making them TRUE/FALSE would be simpler (similar to BOOL vs BOOLEAN, but different since the latter are typed).Curious: a lot of programs use glib to get around this kind of thing (booleans, machine word-size differences, unified interfaces for things like regular expressions, etc.). Have you guys considered it?The BOOL vs BOOLEAN stuff is in an area where glib fails to help (native Win32 ports).
The best idea IMO is to check for "bool". If it's not there, typedef it. If it is, just use it as is (even some pre-C99 compilers have it.) It's just a single autoconf line:
AC_CHECK_TYPES(bool) Then in your header file: #ifndef HAVE_BOOL enum booleanValues { false, true }; typedef enum booleanValues bool; #endif Then simply use bool, true and false as if you're always on C99 or C++.
[Prev in Thread] | Current Thread | [Next in Thread] |