Changes between Version 5 and Version 6 of j2p

Timestamp:

06/07/23 14:15:49 (18 months ago)

Author:

wouter

Comment:

--

j2p

@@ -26 +26 @@
 
 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.
+
+
+== Usage
+Comments can contain python code if the block starts with {@link #CODE_IN_COMMENT_TXT}. This code replaces the entire object (if/case/while block; statement) that follows the comment.
+
+Python has strict requirements regarding indentation. To make this possible, we need to be strict about indentation as well. In a single line python comment, the code must look exactly like
+
+{{{
+ //#PY single_python_line 
+}}}
+
+  Note the single whitespace after the #PY. Your code starts after this single whitespace.
+
+ In a multi line comment the code must look exactly like
+{{{
+/*#PY
+ * codeline1
+ * codeline2
+ * ...
+ */
+}}}
+
+Your code lines each start with "* ", note the whitespace after the star. You are free to indent before the "*".
+
+Your code is automatically indented to the level needed at the insertion
+ place in the coed.
+
+Code MUST be placed in either a standard block comment or a single line
+comment. Starting a javadoc with the {@link #CODE_IN_COMMENT_TXT} is not
+allowed. This is to encourage proper use of javadoc.
+ 
+  A comment block overrides also annotations.
+
+ If the code block contains no code at all, it is translated as
+ {{{pass}}}, to ensure that the code is a proper statement.
+
+
+
+
+
+
+== Resulting file