query: c++ - prevent name mangling for WebAssembly
positive_passages.docid: 27462
positive_passages.text: How can i avoid name mangling?
negative_passages.docid: 95568
negative_passages.text: Is there a way to set GWT to include style names in the compiled names?
negative_passages.docid: 101523
negative_passages.text: Why is using `<<-` frowned upon and how can I avoid it?
negative_passages.docid: 48874
negative_passages.text: ASP.NET MVC Namespace renaming
negative_passages.docid: 130545
negative_passages.text: In C++, what is a "namespace alias"?
negative_passages.docid: 131467
negative_passages.text: Use types of same name & namespace in 2 .NET assemblies
negative_passages.docid: 18856
negative_passages.text: How can I protect my .NET assemblies from decompilation?
negative_passages.docid: 72062
negative_passages.text: Is it possible to prevent stack allocation of an object and only allow it to be instantiated with 'new'?
negative_passages.docid: 12542
negative_passages.text: Why aren't my compile guards preventing multiple definition inclusions?
negative_passages.docid: 41842
negative_passages.text: Is it possible to avoid repeating the class name in the implementation file?
negative_passages.docid: 20368
negative_passages.text: Unmangling the result of std::type_info::name
negative_passages.docid: 34420
negative_passages.text: What is the best way to solve an Objective-C namespace collision?
negative_passages.docid: 125508
negative_passages.text: Getting base name of the source file at compile time
negative_passages.docid: 105196
negative_passages.text: Repeated Multiple Definition Errors from including same header in multiple cpps
negative_passages.docid: 144141
negative_passages.text: Platform-independent GUID generation in C++?
negative_passages.docid: 20446
negative_passages.text: How do I construct a "named character" programmatically?
negative_passages.docid: 107911
negative_passages.text: How should I detect unnecessary #include files in a large C++ project?