jean pierre Lerbscher comments

Results 339 comments of


                                            jean pierre Lerbscher

Solve method declarations in anonymous inner classes

> But in another example, I find this type-based approach problematic. When solving the method call expression obj.print(), the result is Parent.print(). Although the type of obj is Parent, the...

TypeParameter (after extends/implements) parsed as ClassOrInterfaceType

Is this answer correct or should we identify it as a bug.

Use less volatile test setup

Hi, It seems to me that these 2 test classes globally test different versions of JP based on the method calls. The intentions of this PR are not very clear...

LexicalPreservingPrinter misses whitespaces when re-ordering Modifiers

For information, this is indeed a bug in LPP for which I have not yet found a satisfactory solution. It is caused when taking into account the difference between the...

LexicalPreservingPrinter misses whitespaces when re-ordering Modifiers

> For information, this is indeed a bug in LPP for which I have not yet found a satisfactory solution. It is caused when taking into account the difference between...

ReflectionTypeSolver.tryToSolveType(int[].class.getName()) fails

In Javaparser there is no type declaration available for an Array.

Hi ,sometimes(not every times, very small percent possibility) parse will cause stackoverflow error

Hi @Yelixing Without a simple test case that reproduces the anomaly we cannot work on this issue.

Adding type annotation with Lexical Preserving Printer

It seems to me that on the VariableDeclarator node you can get the Type and set a list of annotations. You can also create or modify annotations from FieldDeclaration.

Adding type annotation with Lexical Preserving Printer

Your analysis is correct. Unfortunately I don't think this problem can be solved easily. With lexical preservation, the calculation of the difference between 2 nodes of the AST resulting from...

Adding type annotation with Lexical Preserving Printer

I think it's just something that was not planned. This part of the code is too complex to try to implement this kind of functionality that no one but you...