Output: Place inline namespace members in containing namespace

An inline namespace affects the linkage of its members but for APIs
the members are effectively in the containing namespace.  Generate
output as if they were really in the containing namespace and do
not generate a Namespace element for an inline namespace.

If --castxml-start names an inline namespace simply ignore it to avoid
dumping a Namespace element for it.  One can argue this is valid since
the inline namespace should not normally be named in API usage.

Set our printing policy to avoid showing the inline namespace component
automatically.  Note that expressions in the source code that hard-code
the inline namespace name will still be preserved and show the inline
namespace when printed (e.g. Variable init="" attribute expressions).

Suggested-by: Michka Popoff <michkapopoff@gmail.com>

1 files changed, 8 insertions, 0 deletions

diff --git a/test/expect/gccxml.any.Namespace-inline.xml.txt b/test/expect/gccxml.any.Namespace-inline.xml.txt
new file mode 100644
index 0000000..f54e7a7
--- /dev/null
+++ b/test/expect/gccxml.any.Namespace-inline.xml.txt
@@ -0,0 +1,8 @@
+^<\?xml version="1.0"\?>
+<GCC_XML[^>]*>
+  <Namespace id="_1" name="start" context="_2" members="_3 _4"/>
+  <Struct id="_3" name="A" context="_1" location="f1:4" file="f1" line="4" incomplete="1"/>
+  <Struct id="_4" name="B" context="_1" location="f1:6" file="f1" line="6" incomplete="1"/>
+  <Namespace id="_2" name="::"/>
+  <File id="f1" name=".*/test/input/Namespace-inline.cxx"/>
+</GCC_XML>$