summaryrefslogtreecommitdiff
path: root/handy.h
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-02-19 16:02:40 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-02-19 16:02:40 +0000
commitc1d22f6b609261e5abd7381bd017773c7ae58346 (patch)
tree73d4d872c548dc482f54068017679abb19fdc7c6 /handy.h
parent9a34ef1dede5fef4f3211de7a12cc37f4645a3bd (diff)
downloadperl-c1d22f6b609261e5abd7381bd017773c7ae58346.tar.gz
don't blindly set bool=char on linux (from Andy Dougherty)
p4raw-id: //depot/perl@5144
Diffstat (limited to 'handy.h')
-rw-r--r--handy.h23
1 files changed, 12 insertions, 11 deletions
diff --git a/handy.h b/handy.h
index ce2631f9d2..2c5d706de4 100644
--- a/handy.h
+++ b/handy.h
@@ -48,18 +48,18 @@ Null SV pointer.
just figure out all the headers such a test needs.
Andy Dougherty August 1996
*/
-/* bool is built-in for g++-2.6.3, which might be used for an extension.
- If the extension includes <_G_config.h> before this file then
- _G_HAVE_BOOL will be properly set. If, however, the extension includes
- this file first, then you will have to manually set -DHAS_BOOL in
- your command line to avoid a conflict.
+/* bool is built-in for g++-2.6.3 and later, which might be used
+ for extensions. <_G_config.h> defines _G_HAVE_BOOL, but we can't
+ be sure _G_config.h will be included before this file. _G_config.h
+ also defines _G_HAVE_BOOL for both gcc and g++, but only g++
+ actually has bool. Hence, _G_HAVE_BOOL is pretty useless for us.
+ g++ can be identified by __GNUG__.
+ Andy Dougherty February 2000
*/
-#ifdef _G_HAVE_BOOL
-# if _G_HAVE_BOOL
+#ifdef __GNUG__ /* GNU g++ has bool built-in */
# ifndef HAS_BOOL
-# define HAS_BOOL 1
+# define HAS_BOOL 1
# endif
-# endif
#endif
/* The NeXT dynamic loader headers will not build with the bool macro
@@ -81,6 +81,7 @@ Null SV pointer.
# else
# define bool char
# endif
+# define HAS_BOOL 1
#endif
/* XXX A note on the perl source internal type system. The
@@ -466,10 +467,10 @@ typedef U16 line_t;
#endif
-/* This looks obsolete (IZ):
-
+/*
XXX LEAKTEST doesn't really work in perl5. There are direct calls to
safemalloc() in the source, so LEAKTEST won't pick them up.
+ (The main "offenders" are extensions.)
Further, if you try LEAKTEST, you'll also end up calling
Safefree, which might call safexfree() on some things that weren't
malloced with safexmalloc. The correct "fix" to this, if anyone