Changes between Version 53 and Version 54 of j2p

Timestamp:

12/07/23 12:16:19 (12 months ago)

Author:

wouter

Comment:

--

j2p

@@ -32 +32 @@
 
 
-The mechanism assumes a fixed mapping from java classes to python classes, as in the table below. Also it is assumed that the equivalent classes have roughly the same functionality, even if the actual function names and arguments may differ. This fixed mapping is needed to ensure the translator can be sure which classes will appear on the python side of the translation, so that proper actions can be taken to further the translation.
+The mechanism is flexible in its mapping from java classes to python classes. 
+The general approach is to assume a fixed mapping from java classes to python classes, as in the table below. Also it is assumed that the equivalent classes have roughly the same functionality, even if the actual function names and arguments may differ. This fixed mapping simplifies translation.
+
+But the translator can intercept special classes and make dedicated translations. For instance if a class C is implementing {{{Iterator}}} and it is of class C, translating {{{it.next()}}} gives {{{next(it)}}}, and the definition {{{void iterator()}}} translates to {{{__iter__(self)}}}. 
 
 ==== constructs