Java 1-14 Parser and Abstract Syntax Tree for Java, including preview features to Java 13.
Thanks
I saw this, to update antlr grammar, as it's till stuck at java 9. I thought it might interest the group - but cannot sell if actual progress was made though :( https://summerofcode.withgoogle.com/archive/2020/projects/4999687213416448/
looks like the student didn't do it ;( https://github.com/search?q=user%3ANickCuso+antlr
hmm he's added it to his linkedin https://www.linkedin.com/in/nick-mancuso-961352170/ maybe it's not public. will ping him.
Hey @jessechen09 - since you have checked out the source code of JavaParser, are you going to modify it? Maybe it is interesting for the JavaParser project?
I'm using javaparser to create ASTs, as we need ASTs for our research project. That said I don't think I'll modify it, unless there is a feature that's missing and is an easy fix.
In the Node class's toString() method, it prints out the node AND its children, so if I toString() a CompilationUnit, it should print out the whole AST, right? However, I am only getting the original class's code. Did I misunderstand something or did I do something wrong? Thanks
3 replies
I cant seem to find this in any documentation but how do you add java.lang.* and javax.* Type Declarations to the compilation unit?
or is there a way to check if a type, found by parsing source code, extends a java.lang.* and javax.* class?
I did set the ReflectionTypeSolver for my parser but java.lang.* and javax.* classes are unresolvable. This prevents me from using isAssignable to determine inheritance.
Hi all! I'd like to know if it is possible to parse some Expression Language using the JavaParser. While most of the SimpleJavaParse.parseExpression() would work just fine, they have added some changes to the change, like enabling using "eq" instead of "==", and they have added a new syntax for Lists and Sets ([1,2,3,4], {1,2,3}) and for Map ({"key":"value"}).
In this case it is still possible to use the JavaParser?
antlr sounds like it could potentially be a good option too, though I think the latest java grammar isn't very recent
I have a prototype using ANTLR, but I'd like to reuse other code instead of implementing the Lexer, parser and stuff
e.g. if
Duck is in the package headfirst.strategy, the source root will be the folder above headfirst(i.e. the src directory)
1 reply
Shall I put it on Twitter?
Several people asked if JP has data flow graph/diagram/analysis support, and I wondered how much effort it would be to build it. It's now in a state that the design is right - lots of stuff still missing though - so I thought I would make it public: https://github.com/matozoid/data_flow_analyser_with_javaparser
Feel free to help/comment/ignore :-)
Hi, I'm currently trying to instrument code for monitoring using Javaparser. Therefore, I need to know whether a statement is considered as unreachable by the compiler or not (to eventually add a return statement). From what I've seen now, https://github.com/javaparser/javaparser/blob/master/javaparser-symbol-solver-core/src/main/java/com/github/javaparser/symbolsolver/resolution/typeinference/ControlFlowLogic.java should do this job, but is not implemented yet. Are there other options for doing this with javaparser (besides implementing
ControlFlowLogic myself)?
Thanks to @jlerbsc for teaching me a new word :-) https://en.wikipedia.org/wiki/Schmilblick
4 replies
I saw a discussion on the web somewhere about adding Kotlin support to JavaParser. Has there been any work done on this?
Hi, I’m working on a static code analyser (e2immu.org) that uses JavaParser as its source code parser. To be able to analyse its own code, e2immu would need Java 16 language features. I’m not using the JavaParser’s symbol solver. Could you please point me to a time-line for JavaParser’s Java 16 language support? I would consider helping a hand if that can speed things up.
7 replies
Hey, I just opened an issue (javaparser/javaparser#3244) but realised this might actually be a better place for it. I'm struggling with an
OrphanComment in a BlockStmt, it doesn't appear when added programmatically (it does output correctly when it's in the parsed file). My project was still stuck on V3.6 of the parser and there it worked fine, but now that I'm upgrading to the latest version all of a sudden the comment fully disappears, leaving behind an empty block. Is this a regression or should I create a block that only contains a comment in another way?
15 replies
If not sooner
