Changes between Version 32 and Version 33 of j2p

Timestamp:

06/21/23 11:18:56 (17 months ago)

Author:

wouter

Comment:

--

j2p

@@ -30 +30 @@
 The mechanism assumes a fixed mapping from java to python objects, as in the table below. This fixed mapping is needed to ensure the translator can be sure which objects will appear on the python side of the translation, so that proper actions can be taken to further the translation.
 
-built-in "primitives"
+==== constructs
+The {{{private}}} keyword is reflected by the python convention of adding "__" to private fields function names and method names
+
+The {{{static}}} keyword results in fields being set in the class definition object. 
+
+Fields in Java have to be initialized in the __init__ function in the python translation.
+
+Overloaded methods can not be handled by default python and need to be handled using an external library {{{multidispatch==0.6.0}}} and result in additional annotations {{{@dispatch(...)}}} in the translated code.
+
+==== built-in "primitives"
 ||=java=||=python=||=remarks=||
 ||String||str||
@@ -39 +48 @@
 ||Set||set||
 
-built-in classes
+==== built-in classes
 ||=java=||=python=||=remarks=||
 ||Class||type||
@@ -46 +55 @@
 If function calls in python deliver a wrong object (not matching the above mapping), the translator has to inject additional code to convert it to the proper object. For example, {{{Map.getKeys()}}} in python would be {{{set(map.keys())}}} where the extra {{{set}}} converts the dict_keys into a proper set.
 
-Some more notes:
+==== More notes:
 * some classes like {{{Arrays}}} or {{{Override}}} do not have a direct python equivalent. calls to static functions in these classes can still be translated. 
 * Different java classes, eg {{{Map}}} {{{AbstractMap}}} and {{{HashMap}}}, may translate to the same python class ({{{map}}}). This can be done because  translation is only 1 way.