Changes between Version 74 and Version 75 of j2p

Timestamp:

05/16/24 10:42:59 (11 months ago)

Author:

wouter

Comment:

--

j2p

@@ -125 +125 @@
 Java variables like {{{String val}}} can contain a null value, and functions like {{{String f() { ... } }}} can return null. Therefore they are translated to {{{val:Optional[str]}}} and {{{def f(self)->Optional[str]}}}.
 You can annotate the java code with {{{@NonNull}}} (from {{{org.eclipse.jdt.annotation.NonNull}}}) to indicate the value/return value will not be null, like this
-{{{@NonNull String val}}} or {{{@NonNull String f() { ... } }}}. Java primitive types like {{{boolean}}} and {{{int}}} can never be null and do not need @{{{@NonNull}}}
+{{{@NonNull String val}}} or {{{@NonNull String f() { ... } }}}. Java primitive types like {{{boolean}}} and {{{int}}} can never be null and do not need {{{@NonNull}}}
 
 The dependency needed for this is (unfortunately this annotation is not built in anymore in the JRE)
@@ -144 +144 @@
 
 {{{#!td style="background: #efe"
-@{{{@NonNull}}} can be used by the java compiler to do extra checks on your code. Eclipse uses this annotation by default, but you may need to enable or customize it in Preferences/Java/Compiler/Errors/Warnings and scroll down to "Null Analysis".
+{{{@NonNull}}} can be used by the java compiler to do extra checks on your code. Eclipse uses this annotation by default, but you may need to enable or customize it in Preferences/Java/Compiler/Errors/Warnings and scroll down to "Null Analysis".
 }}}
 
 {{{#!td style="background: #fee"
-@{{{@NonNull}}} is NOT inherited by subclasses. Therefore @{{{@NonNull}}} has to be repeated in the derived classes.
+{{{@NonNull}}} is NOT inherited by subclasses. Therefore {{{@NonNull}}} has to be repeated in the derived classes.
 }}}