Bck2BrwsrMangling
From APIDesign
(Difference between revisions)
(New page: When translating the ByteCode to JavaScript the Bck2Brwsr project needs to face a common problem -- when translating a typed language (like Java) to untyped (like [[JavaScr...) |
(→Like JNI) |
||
| Line 3: | Line 3: | ||
== Like [[JNI]] == | == Like [[JNI]] == | ||
| - | There is a common [[wikipedia:Name_mangling|mangling scheme]] specified by [[JNI]] for [[C]]. | + | There is a common [[wikipedia:Name_mangling|mangling scheme]] specified by [[JNI]] for [[C]] and [[Bck2Brwsr]] mimics the [http://docs.oracle.com/javase/1.5.0/docs/guide/jni/spec/design.html specification] as closely as possible. |
Revision as of 12:07, 26 January 2013
When translating the ByteCode to JavaScript the Bck2Brwsr project needs to face a common problem -- when translating a typed language (like Java) to untyped (like JavaScript) one needs to mange the names, so they continue to support method and field overloading.
Like JNI
There is a common mangling scheme specified by JNI for C and Bck2Brwsr mimics the specification as closely as possible.
Follow
