Changes between Version 151 and Version 152 of j2p

Timestamp:

10/29/24 15:31:25 (4 weeks ago)

Author:

wouter

Comment:

--

j2p

@@ -313 +313 @@
 * 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.
 * Other classes, like PriorityQueue, have no equivalent python class, and use a special class to help the translation
-* Some methods, return a 'second class citizen' which leads to compatibility issues later in the code. We may replace some of these calls with alternatives. For example, in python dict.keys() returns a slimmed-down version of "set", which fails if you try to call eg "remove". In this case we use Keys(dict) from the utilitiespy package as a replacement.
+* Some methods, return a 'second class citizen' which leads to compatibility issues later in the code. We may replace some of these calls with alternatives. For example, in python dict.keys() returns an object that somewhat resembles a set" but can't be used as such. In this case we use {{{Keys(dict)}}} from the utilitiespy package as a replacement.
 * The imported libraries in python have a different name than those in java. If the python library name equals the name of some variable in your code, this will cause a runtime error, typically something like {{{local variable 'json' referenced before assignment}}}. We can not (yet?) detect these issues at compile time. To solve it, change the variable name in java.