Compiler switch to put generated Haxe classes into a child namespace

Currently hxcpp places many classes in the root C++ namespace. Many of these classes have common names like "String", "File", "Object", and "Class". This creates conflicts between hxcpp and other C++ code. The lack of namespace-compliance also makes hxcpp unreliable for production code, because there is no guarantee that its output will work with existing, namespace-compliant code bases.

Ideally in the long run these classes would be put into a child namespace by default, but since so far hxcpp has been using the root namespace, the only viable solution now would be a compiler switch that toggles which namespace (root or child) the generated Haxe classes are placed in.

L’issue non indica file, test né un punto di ingresso del compilatore. Traccia dove hxcpp gestisce i namespace delle classi generate e dove sono definiti gli switch del compilatore, quindi determina come la scelta tra il namespace radice e quello figlio debba essere resa disponibile e verificata per classi generate come String, File, Object e Class.

Scritto dal modello di indicizzazione a partire dal testo della issue.