Changes between Version 24 and Version 25 of j2p

Timestamp:

06/20/23 11:30:38 (20 months ago)

Author:

wouter

Comment:

--

j2p

@@ -15 +15 @@
 
 == Internal mechanism
-There are two main components in the core:
-1. The translator that parses java code and creates equivalent python code
-2. per-java-class translators that know how to translate a specific call to a java class function or field into equivalent python code. 
+Translation is done on a per-java-file basis. 
 
-The first is generic and used for all java programs. It is currently pretty complete but details will be filled in over time as the need arises to support more java syntax.
+There are two main translation components in the core:
+1. The translator that parses java file with [https://github.com/javaparser/javaparser Javaparser] and creates equivalent python code.
+2. per-java-class translators that know how to translate all calls to any java class method or field into equivalent python code. This code is using introspection and assumes all used java classes are available, either through libraries or from the java compiler.
 
-The second is currently very partial. The reason is that there are a huge number of java classes, and every field and function in it will need a specialized translator. This will grow slowly over time as needed.
+(1) generic and used for all java programs. It is currently pretty complete but details will be filled in over time as the need arises to support more java syntax.
+
+(2) is currently very partial. The reason is that there are a huge number of java classes and even more 3rd party libraries, and almost every field and function in it will need a specialized translator. This will grow slowly over time as needed.