C++ bindings

mojo/public/bindings/sample_service.idl

Index: mojo/public/bindings/sample_service.idl
diff --git a/mojo/public/bindings/sample_service.idl b/mojo/public/bindings/sample_service.idl
new file mode 100644
index 0000000000000000000000000000000000000000..11bf7d0eac344036bec1c905652bac441f2e4565
--- /dev/null
+++ b/mojo/public/bindings/sample_service.idl
@@ -0,0 +1,30 @@
+// 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.
+
+// HYPOTHETICAL IDL:
+
+module sample {
+
+struct Bar {
+  alpha @0 :uint8;
+  beta @1 :uint8;
+  gamma @2 :uint8;
+};

[viettrungluu, 2013/10/01 00:51:04]

Are we going to support ...

- ... "enums"? Enumerations that get checked properly are probably a
usability/security win.
- ... inner structs? (Side comment: protoc declares an inner struct/message
Foo::Bar as Foo_Bar + a typedef to allow Foo::Bar to be used, which is nice
since it allows Foo_Bar to be forward-declared.
- ... inner (nested) namespaces?
- ... importing other IDL files? (Side comment: The latest protobufs
distinguishes between "import" and "import public", which is nice.
Forward-declarability is required for this.)

(Protobufs support all of these. Probably some of my questions have been
answered somewhere, but I'm too lazy to dig through design docs at the moment.)

+
+struct Foo {
+  x @0 :int32;
+  y @1 :int32;
+  a @2 :bool;
+  b @3 :bool;
+  c @4 :bool;
+  bar @5 :Bar;
+  extra_bars @7 :array(Bar) [optional];
+  data @6 :array(uint8);
+};
+
+interface Service {
+  Frobinate @0 (foo @0 :Foo, baz @1 :bool);
+};
+
+}