Mojo C++ bindings

mojo/public/system/macros.h

+// Copyright 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef MOJO_PUBLIC_SYSTEM_MACROS_H_
+#define MOJO_PUBLIC_SYSTEM_MACROS_H_
+
+#ifdef __cplusplus
+
+namespace mojo {
+
+// Annotate a virtual method indicating it must be overriding a virtual
+// method in the parent class.
+// Use like:
+//   virtual void foo() OVERRIDE;
+#if defined(_MSC_VER)
+#define MOJO_OVERRIDE override
+#elif defined(__clang__)

[dmichael (off chromium), 2013/10/14 22:41:19]

nit: Could just use:
#if defined(_MSV_VER) || defined(__clang__)

+#define MOJO_OVERRIDE override
+#else
+#define MOJO_OVERRIDE
+#endif
+
+// A macro to disallow the copy constructor and operator= functions
+// This should be used in the private: declarations for a class
+#define MOJO_DISALLOW_COPY_AND_ASSIGN(TypeName) \
+  TypeName(const TypeName&);                    \
+  void operator=(const TypeName&)
+
+// Used to assert things at compile time.
+namespace internal { template <bool> struct CompileAssert {}; }
+#define MOJO_COMPILE_ASSERT(expr, msg) \
+    typedef internal::CompileAssert<(bool(expr))> msg[bool(expr) ? 1 : -1]

[dmichael (off chromium), 2013/10/14 22:41:19]

nit: This is kind of a weird mix of static assert techniques to me. What's the
point of CompileAssert? It seems like you could juse use any fundamental type
like char and get the same effect in a way that's C-compatible:
typedef char msg[bool(expr) ? 1 : -1];

The kind of canonical C++ way is to do:
template <bool value>
struct CompileAssert;

template <>
struct CompileAssert<true> {};

(I.e., only provide a "true" specialization CompileAssert so that a false will
cause a compile error that there's no valid specialization for "false".)

In the code here, I don't see the purpose of the CompileAssert struct.

+
+}  // namespace mojo
+
+#endif  // __cplusplus
+
+#endif  // MOJO_PUBLIC_SYSTEM_MACROS_H_