AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

Get rid of the unused __my_bool__ macro.

Browse Source 
R=svenpanne@chromium.org

Review URL: https://codereview.chromium.org/770163002

Cr-Commit-Position: refs/heads/master@{#25593}
This commit is contained in:
bmeurer 2014-12-01 23:25:36 -08:00 committed by Commit bot
parent 643c24eb95
commit d45ed61f43
1 changed files with 0 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
src/globals.h
View File

@ -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;