jean pierre Lerbscher

This issue is definitely related to how comments are handled. Comments are processed before any other token to take into account end-of-line comments. In fact, it would suffice to differentiate...

Hi @4everTheOne Thank you for this contribution. It seems to me that this PR contains many changes that are not dependent on each other. It is difficult to validate in...

I don't knwo why i see more difference. Anyway since the changes are related it is better to keep them in the same commit. I let @MysterAitch validate this PR...

Hi @4everTheOne I'm not a fan of this solution because it multiplies the number of methods in the JavaParser class. Wouldn't it be possible to instead create a new implementation...

Hi @Maccimo to keep the initial presentation you must use LexicalPreservingPrinter.

Hi @Maccimo have you tried using LexicalPreservingPrinter!?

Hi @corradomio did the fix solve your issue? If yes, could you close your issue please?

@liuyuanOUC, As far as I understand JP there is no declaration corresponding to System in your example. If you want to know the type you can use calculateResolvedType method. System.out.println(ne.calculateResolvedType().describe());...

@liuyuanOUC In this statement "System.out.println(name);" name is a NameExpr. If symbolsolver is configured all expressions that implement the Resolvable interface can be resolved and it allows you to access the...

@liuyuanOUC First JavaParserTypeSolver must point to the src directory but it's not related to your issue. You don't need to set the rt.jar typeSolver.add(new JavaParserTypeSolver(new File("D:\\testJavaparser\\src\\main\\java"))); "If the declaration corresponding...