Package org.bridj.demangling

BridJ symbols demanglers.

See:
Description

Interface Summary

Demangler.Annotations
Demangler.IdentLike
Demangler.TemplateArg

Class Summary

Demangler	Base class and core structures for symbol demanglers (typically, for C++ symbols).
Demangler.ClassRef
Demangler.Constant
Demangler.FunctionTypeRef
Demangler.Ident
Demangler.JavaTypeRef
Demangler.MemberRef
Demangler.NamespaceRef
Demangler.PointerTypeRef
Demangler.Symbol
Demangler.TypeRef
GCC4Demangler
VC9Demangler

Enum Summary

Demangler.SpecialName

Exception Summary

Package org.bridj.demangling Description

BridJ symbols demanglers.

BridJ adheres to a "reverse burder of proof" philosophy : rather than asking binding makers (including JNAerator) to write/generate the exact expected symbols in Symbol annotations, it parses the mangled symbols and sees how / if they match binding signatures. Manual specification of exact symbols is still possible in case of ambiguity or when demangling fails.

As a consequence, BridJ needs symbols demanglers, which have to parse symbols and spit out (partial) methods and types signatures.
It currently has demanglers for :

• Microsoft Visual C++ (2008, 2010)
• GCC 4.x (which mangling scheme is fortunately shared by Intel's C++ compiler) : its mangling scheme does not include the return type of functions / methods, which is infortunate (would have allowed dynamic languages to call C++ without explicit bindings, otherwise :-( )