From d45ed61f43e4f303b2f8cbe2d40b752c0c976b04 Mon Sep 17 00:00:00 2001 From: bmeurer Date: Mon, 1 Dec 2014 23:25:36 -0800 Subject: [PATCH] Get rid of the unused __my_bool__ macro. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/770163002 Cr-Commit-Position: refs/heads/master@{#25593} --- src/globals.h | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/src/globals.h b/src/globals.h index 9a071971db..01169d88df 100644 --- a/src/globals.h +++ b/src/globals.h @@ -89,22 +89,6 @@ namespace internal { #define V8_DOUBLE_FIELDS_UNBOXING 0 #endif -// Support for alternative bool type. This is only enabled if the code is -// compiled with USE_MYBOOL defined. This catches some nasty type bugs. -// For instance, 'bool b = "false";' results in b == true! This is a hidden -// source of bugs. -// However, redefining the bool type does have some negative impact on some -// platforms. It gives rise to compiler warnings (i.e. with -// MSVC) in the API header files when mixing code that uses the standard -// bool with code that uses the redefined version. -// This does not actually belong in the platform code, but needs to be -// defined here because the platform code uses bool, and platform.h is -// include very early in the main include file. - -#ifdef USE_MYBOOL -typedef unsigned int __my_bool__; -#define bool __my_bool__ // use 'indirection' to avoid name clashes -#endif typedef uint8_t byte; typedef byte* Address;