name-mangling

Is it possible to unmangle names like these in Delphi? If so, where do I get more information? Example of an error message where it cannot find a certain entry in the dbrtl100.bpl I want to know which exact function it cannot find (unit, class, name, parameters, etc). --------------------------- myApp.exe - Entry Point Not Found --------------------------- The procedure entry point @Dbcommon@GetTableNameFromSQLEx$qqrx17System@WideString25Dbcommon@IDENTIFIEROption could not be located in the dynamic link library dbrtl100.bpl. --------------------------- OK --------------------------- I know it

class foo { public: void say_type_name() { std::cout << typeid(this).name() << std::endl; } }; int main() { foo f;; f.say_type_name(); } Above code prints P3foo on my ubuntu machine with g++. I am not getting why it is printing P3foo instead of just foo . If I change the code like std::cout << typeid(*this).name() << std::endl; it prints 3foo . Any thoughts? Because it is a pointer to foo. And foo has 3 characters. So it becomes P3foo . The other one has type foo , so it becomes 3foo . Note that the text is implementation dependent, and in this case GCC just gives you the internal, mangled

Python provides private name mangling for class methods and attributes. Are there any concrete cases where this feature is required, or is it just a carry over from Java and C++? Please describe a use case where Python name mangling should be used, if any? Also, I'm not interested in the case where the author is merely trying to prevent accidental external attribute access. I believe this use case is not aligned with the Python programming model. It's partly to prevent accidental internal attribute access. Here's an example: In your code, which is a library: class YourClass: def __init__(self)

In Scala, what's the best way to dynamically instantiate an object and invoke a method using reflection? I would like to do Scala-equivalent of the following Java code: Class class = Class.forName("Foo"); Object foo = class.newInstance(); Method method = class.getMethod("hello", null); method.invoke(foo, null); In the above code, both the class name and the method name are passed in dynamically. The above Java mechanism could probably be used for Foo and hello() , but the Scala types don't match one-to-one with that of Java. For example, a class may be declared implicitly for a singleton

I am trying to learn and understand name mangling in C++. Here are some questions: (1) From devx When a global function is overloaded, the generated mangled name for each overloaded version is unique. Name mangling is also applied to variables. Thus, a local variable and a global variable with the same user-given name still get distinct mangled names. Are there other examples that are using name mangling, besides overloading functions and same-name global and local variables ? (2) From Wiki The need arises where the language allows different entities to be named with the same identifier as