Changes between Version 168 and Version 169 of j2p


Ignore:
Timestamp:
11/18/24 12:36:26 (7 days ago)
Author:
wouter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • j2p

    v168 v169  
    536536||I get UnsolvedSymbolException{context='null', name='We are unable to find the method declaration corresponding to ...||Sometimes the javaparser we use has a problem. Nothing we can do about that. For the moment you will have to manually translate problem spots to python with #PY.||
    537537||I get an error in python on an overloaded method ({{{@dispatch}}}), incorrect number of arguments.||{{{@dispatch}}} has a problem with Optional arguments. Try making the arguments {{{@NonNull}}} in java.||
    538 ||I get an UnsupportedOperationException inside javaparser LambdaExprContext||Javaparser seems to sometimes have trouble with resolving argument types inside lambda expressions. Try explicitly naming the left side of your lambda expression||
    539538||I get {{{Method '...' cannot be resolved in context ...}}} from the javaparser||The javaparser has problems resolving the method when the provided argument does exactly not match the actual argument, eg when your method call uses an int while the actual method takes a long. Try changing your call so that the argument type is exactly matching the method type.||
     539||I get an {{{UnsupportedOperationException}}} inside javaparser LambdaExprContext||Javaparser seems to sometimes have trouble with resolving argument types inside lambda expressions. Try explicitly typing the left side of your lambda expression||