Speculative fix for the white/stale tab issue on Windows.
[chromium-blink-merge.git] / base / basictypes.h
blob821055447222921dfba705473cc8d9a15226a997
1 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file.
5 #ifndef BASE_BASICTYPES_H_
6 #define BASE_BASICTYPES_H_
8 #include <limits.h> // So we can set the bounds of our types
9 #include <stddef.h> // For size_t
10 #include <string.h> // for memcpy
12 #include "base/port.h" // Types that only need exist on certain systems
14 #ifndef COMPILER_MSVC
15 // stdint.h is part of C99 but MSVC doesn't have it.
16 #include <stdint.h> // For intptr_t.
17 #endif
19 typedef signed char schar;
20 typedef signed char int8;
21 typedef short int16;
22 typedef int int32;
24 // The NSPR system headers define 64-bit as |long| when possible, except on
25 // Mac OS X. In order to not have typedef mismatches, we do the same on LP64.
27 // On Mac OS X, |long long| is used for 64-bit types for compatibility with
28 // <inttypes.h> format macros even in the LP64 model.
29 #if defined(__LP64__) && !defined(OS_MACOSX) && !defined(OS_OPENBSD)
30 typedef long int64;
31 #else
32 typedef long long int64;
33 #endif
35 // NOTE: unsigned types are DANGEROUS in loops and other arithmetical
36 // places. Use the signed types unless your variable represents a bit
37 // pattern (eg a hash value) or you really need the extra bit. Do NOT
38 // use 'unsigned' to express "this value should always be positive";
39 // use assertions for this.
41 typedef unsigned char uint8;
42 typedef unsigned short uint16;
43 typedef unsigned int uint32;
45 // See the comment above about NSPR and 64-bit.
46 #if defined(__LP64__) && !defined(OS_MACOSX) && !defined(OS_OPENBSD)
47 typedef unsigned long uint64;
48 #else
49 typedef unsigned long long uint64;
50 #endif
52 // A type to represent a Unicode code-point value. As of Unicode 4.0,
53 // such values require up to 21 bits.
54 // (For type-checking on pointers, make this explicitly signed,
55 // and it should always be the signed version of whatever int32 is.)
56 typedef signed int char32;
58 const uint8 kuint8max = (( uint8) 0xFF);
59 const uint16 kuint16max = ((uint16) 0xFFFF);
60 const uint32 kuint32max = ((uint32) 0xFFFFFFFF);
61 const uint64 kuint64max = ((uint64) GG_LONGLONG(0xFFFFFFFFFFFFFFFF));
62 const int8 kint8min = (( int8) 0x80);
63 const int8 kint8max = (( int8) 0x7F);
64 const int16 kint16min = (( int16) 0x8000);
65 const int16 kint16max = (( int16) 0x7FFF);
66 const int32 kint32min = (( int32) 0x80000000);
67 const int32 kint32max = (( int32) 0x7FFFFFFF);
68 const int64 kint64min = (( int64) GG_LONGLONG(0x8000000000000000));
69 const int64 kint64max = (( int64) GG_LONGLONG(0x7FFFFFFFFFFFFFFF));
71 // A macro to disallow the copy constructor and operator= functions
72 // This should be used in the private: declarations for a class
73 #define DISALLOW_COPY_AND_ASSIGN(TypeName) \
74 TypeName(const TypeName&); \
75 void operator=(const TypeName&)
77 // An older, deprecated, politically incorrect name for the above.
78 // NOTE: The usage of this macro was baned from our code base, but some
79 // third_party libraries are yet using it.
80 // TODO(tfarina): Figure out how to fix the usage of this macro in the
81 // third_party libraries and get rid of it.
82 #define DISALLOW_EVIL_CONSTRUCTORS(TypeName) DISALLOW_COPY_AND_ASSIGN(TypeName)
84 // A macro to disallow all the implicit constructors, namely the
85 // default constructor, copy constructor and operator= functions.
87 // This should be used in the private: declarations for a class
88 // that wants to prevent anyone from instantiating it. This is
89 // especially useful for classes containing only static methods.
90 #define DISALLOW_IMPLICIT_CONSTRUCTORS(TypeName) \
91 TypeName(); \
92 DISALLOW_COPY_AND_ASSIGN(TypeName)
94 // The arraysize(arr) macro returns the # of elements in an array arr.
95 // The expression is a compile-time constant, and therefore can be
96 // used in defining new arrays, for example. If you use arraysize on
97 // a pointer by mistake, you will get a compile-time error.
99 // One caveat is that arraysize() doesn't accept any array of an
100 // anonymous type or a type defined inside a function. In these rare
101 // cases, you have to use the unsafe ARRAYSIZE_UNSAFE() macro below. This is
102 // due to a limitation in C++'s template system. The limitation might
103 // eventually be removed, but it hasn't happened yet.
105 // This template function declaration is used in defining arraysize.
106 // Note that the function doesn't need an implementation, as we only
107 // use its type.
108 template <typename T, size_t N>
109 char (&ArraySizeHelper(T (&array)[N]))[N];
111 // That gcc wants both of these prototypes seems mysterious. VC, for
112 // its part, can't decide which to use (another mystery). Matching of
113 // template overloads: the final frontier.
114 #ifndef _MSC_VER
115 template <typename T, size_t N>
116 char (&ArraySizeHelper(const T (&array)[N]))[N];
117 #endif
119 #define arraysize(array) (sizeof(ArraySizeHelper(array)))
121 // ARRAYSIZE_UNSAFE performs essentially the same calculation as arraysize,
122 // but can be used on anonymous types or types defined inside
123 // functions. It's less safe than arraysize as it accepts some
124 // (although not all) pointers. Therefore, you should use arraysize
125 // whenever possible.
127 // The expression ARRAYSIZE_UNSAFE(a) is a compile-time constant of type
128 // size_t.
130 // ARRAYSIZE_UNSAFE catches a few type errors. If you see a compiler error
132 // "warning: division by zero in ..."
134 // when using ARRAYSIZE_UNSAFE, you are (wrongfully) giving it a pointer.
135 // You should only use ARRAYSIZE_UNSAFE on statically allocated arrays.
137 // The following comments are on the implementation details, and can
138 // be ignored by the users.
140 // ARRAYSIZE_UNSAFE(arr) works by inspecting sizeof(arr) (the # of bytes in
141 // the array) and sizeof(*(arr)) (the # of bytes in one array
142 // element). If the former is divisible by the latter, perhaps arr is
143 // indeed an array, in which case the division result is the # of
144 // elements in the array. Otherwise, arr cannot possibly be an array,
145 // and we generate a compiler error to prevent the code from
146 // compiling.
148 // Since the size of bool is implementation-defined, we need to cast
149 // !(sizeof(a) & sizeof(*(a))) to size_t in order to ensure the final
150 // result has type size_t.
152 // This macro is not perfect as it wrongfully accepts certain
153 // pointers, namely where the pointer size is divisible by the pointee
154 // size. Since all our code has to go through a 32-bit compiler,
155 // where a pointer is 4 bytes, this means all pointers to a type whose
156 // size is 3 or greater than 4 will be (righteously) rejected.
158 #define ARRAYSIZE_UNSAFE(a) \
159 ((sizeof(a) / sizeof(*(a))) / \
160 static_cast<size_t>(!(sizeof(a) % sizeof(*(a)))))
163 // Use implicit_cast as a safe version of static_cast or const_cast
164 // for upcasting in the type hierarchy (i.e. casting a pointer to Foo
165 // to a pointer to SuperclassOfFoo or casting a pointer to Foo to
166 // a const pointer to Foo).
167 // When you use implicit_cast, the compiler checks that the cast is safe.
168 // Such explicit implicit_casts are necessary in surprisingly many
169 // situations where C++ demands an exact type match instead of an
170 // argument type convertable to a target type.
172 // The From type can be inferred, so the preferred syntax for using
173 // implicit_cast is the same as for static_cast etc.:
175 // implicit_cast<ToType>(expr)
177 // implicit_cast would have been part of the C++ standard library,
178 // but the proposal was submitted too late. It will probably make
179 // its way into the language in the future.
180 template<typename To, typename From>
181 inline To implicit_cast(From const &f) {
182 return f;
185 // The COMPILE_ASSERT macro can be used to verify that a compile time
186 // expression is true. For example, you could use it to verify the
187 // size of a static array:
189 // COMPILE_ASSERT(ARRAYSIZE_UNSAFE(content_type_names) == CONTENT_NUM_TYPES,
190 // content_type_names_incorrect_size);
192 // or to make sure a struct is smaller than a certain size:
194 // COMPILE_ASSERT(sizeof(foo) < 128, foo_too_large);
196 // The second argument to the macro is the name of the variable. If
197 // the expression is false, most compilers will issue a warning/error
198 // containing the name of the variable.
200 template <bool>
201 struct CompileAssert {
204 #undef COMPILE_ASSERT
205 #define COMPILE_ASSERT(expr, msg) \
206 typedef CompileAssert<(bool(expr))> msg[bool(expr) ? 1 : -1]
208 // Implementation details of COMPILE_ASSERT:
210 // - COMPILE_ASSERT works by defining an array type that has -1
211 // elements (and thus is invalid) when the expression is false.
213 // - The simpler definition
215 // #define COMPILE_ASSERT(expr, msg) typedef char msg[(expr) ? 1 : -1]
217 // does not work, as gcc supports variable-length arrays whose sizes
218 // are determined at run-time (this is gcc's extension and not part
219 // of the C++ standard). As a result, gcc fails to reject the
220 // following code with the simple definition:
222 // int foo;
223 // COMPILE_ASSERT(foo, msg); // not supposed to compile as foo is
224 // // not a compile-time constant.
226 // - By using the type CompileAssert<(bool(expr))>, we ensures that
227 // expr is a compile-time constant. (Template arguments must be
228 // determined at compile-time.)
230 // - The outer parentheses in CompileAssert<(bool(expr))> are necessary
231 // to work around a bug in gcc 3.4.4 and 4.0.1. If we had written
233 // CompileAssert<bool(expr)>
235 // instead, these compilers will refuse to compile
237 // COMPILE_ASSERT(5 > 0, some_message);
239 // (They seem to think the ">" in "5 > 0" marks the end of the
240 // template argument list.)
242 // - The array size is (bool(expr) ? 1 : -1), instead of simply
244 // ((expr) ? 1 : -1).
246 // This is to avoid running into a bug in MS VC 7.1, which
247 // causes ((0.0) ? 1 : -1) to incorrectly evaluate to 1.
250 // bit_cast<Dest,Source> is a template function that implements the
251 // equivalent of "*reinterpret_cast<Dest*>(&source)". We need this in
252 // very low-level functions like the protobuf library and fast math
253 // support.
255 // float f = 3.14159265358979;
256 // int i = bit_cast<int32>(f);
257 // // i = 0x40490fdb
259 // The classical address-casting method is:
261 // // WRONG
262 // float f = 3.14159265358979; // WRONG
263 // int i = * reinterpret_cast<int*>(&f); // WRONG
265 // The address-casting method actually produces undefined behavior
266 // according to ISO C++ specification section 3.10 -15 -. Roughly, this
267 // section says: if an object in memory has one type, and a program
268 // accesses it with a different type, then the result is undefined
269 // behavior for most values of "different type".
271 // This is true for any cast syntax, either *(int*)&f or
272 // *reinterpret_cast<int*>(&f). And it is particularly true for
273 // conversions betweeen integral lvalues and floating-point lvalues.
275 // The purpose of 3.10 -15- is to allow optimizing compilers to assume
276 // that expressions with different types refer to different memory. gcc
277 // 4.0.1 has an optimizer that takes advantage of this. So a
278 // non-conforming program quietly produces wildly incorrect output.
280 // The problem is not the use of reinterpret_cast. The problem is type
281 // punning: holding an object in memory of one type and reading its bits
282 // back using a different type.
284 // The C++ standard is more subtle and complex than this, but that
285 // is the basic idea.
287 // Anyways ...
289 // bit_cast<> calls memcpy() which is blessed by the standard,
290 // especially by the example in section 3.9 . Also, of course,
291 // bit_cast<> wraps up the nasty logic in one place.
293 // Fortunately memcpy() is very fast. In optimized mode, with a
294 // constant size, gcc 2.95.3, gcc 4.0.1, and msvc 7.1 produce inline
295 // code with the minimal amount of data movement. On a 32-bit system,
296 // memcpy(d,s,4) compiles to one load and one store, and memcpy(d,s,8)
297 // compiles to two loads and two stores.
299 // I tested this code with gcc 2.95.3, gcc 4.0.1, icc 8.1, and msvc 7.1.
301 // WARNING: if Dest or Source is a non-POD type, the result of the memcpy
302 // is likely to surprise you.
304 template <class Dest, class Source>
305 inline Dest bit_cast(const Source& source) {
306 // Compile time assertion: sizeof(Dest) == sizeof(Source)
307 // A compile error here means your Dest and Source have different sizes.
308 typedef char VerifySizesAreEqual [sizeof(Dest) == sizeof(Source) ? 1 : -1];
310 Dest dest;
311 memcpy(&dest, &source, sizeof(dest));
312 return dest;
315 // Used to explicitly mark the return value of a function as unused. If you are
316 // really sure you don't want to do anything with the return value of a function
317 // that has been marked WARN_UNUSED_RESULT, wrap it with this. Example:
319 // scoped_ptr<MyType> my_var = ...;
320 // if (TakeOwnership(my_var.get()) == SUCCESS)
321 // ignore_result(my_var.release());
323 template<typename T>
324 inline void ignore_result(const T&) {
327 // The following enum should be used only as a constructor argument to indicate
328 // that the variable has static storage class, and that the constructor should
329 // do nothing to its state. It indicates to the reader that it is legal to
330 // declare a static instance of the class, provided the constructor is given
331 // the base::LINKER_INITIALIZED argument. Normally, it is unsafe to declare a
332 // static variable that has a constructor or a destructor because invocation
333 // order is undefined. However, IF the type can be initialized by filling with
334 // zeroes (which the loader does for static variables), AND the destructor also
335 // does nothing to the storage, AND there are no virtual methods, then a
336 // constructor declared as
337 // explicit MyClass(base::LinkerInitialized x) {}
338 // and invoked as
339 // static MyClass my_variable_name(base::LINKER_INITIALIZED);
340 namespace base {
341 enum LinkerInitialized { LINKER_INITIALIZED };
343 // Use these to declare and define a static local variable (static T;) so that
344 // it is leaked so that its destructors are not called at exit. If you need
345 // thread-safe initialization, use base/lazy_instance.h instead.
346 #define CR_DEFINE_STATIC_LOCAL(type, name, arguments) \
347 static type& name = *new type arguments
349 } // base
351 #endif // BASE_BASICTYPES_H_