Update monster_test.fbs schema with more clear scope resolution example
@@ -13,6 +13,8 @@ namespace MyGame.Example2;
table Monster {} // Test having same name as below, but in different namespace.
+table Strange {}
+
namespace MyGame.Example;
// Note: parent namespace resolution only works without namespace prefix
@@ -21,6 +23,27 @@ namespace MyGame.Example;
// union Foo { Example2.InParentNamespace }
union Foo { InParentNamespace }
+
+namespace MyGame.Example2.SubSystem;
+
+// Note:
+//
+// parent namespace resolution only works without namespace prefix
+// or with a global namespace prefix (a fully qualified name), not
+// something in between.
+// (There is no really good reason for this, it just isn't implemented,
+// and flatc JSON enum parsing works the same way.)
+// The more local name wins any conflict.
+//
+union SubSystemA { Strange }
+union SubSystemB { MyGame.Example2.Strange }
+
+// Works in C++ flatc 1.8 but won't work with flatcc:
+// union SubSystemC { Example2.Strange }
+
+
+namespace MyGame.Example;
+
// test case for negative enum values
enum neg_enum:int {
neg1 = -12,
