New Java-Based Language

Hi! I'm trying to create a new Java-based language with JavaCC. Actually, I can say that I want to write java using my own syntax. I want to use Java libraries in my own language. I want to use this language to do my graduation project at my university.

I also want to use spring boot in this language.

for example in my own language,

@GetMapping(“/findAll”)
def findAll do
     userService.findAll
end

I want to use spring boot.

How can I do this? Is JavaCC the right option? I can also do a language conversion like TypeScript - JavaScript. Can you give me an idea about this subject? Thanks to everyone.

Welcome to the Ranch

Daan Van Den Berg wrote:Hi! I'm trying to create a new . . . language with JavaCC. . . . use spring boot . . . Is JavaCC the right option? . . . .

Until proven otherwise, you should not be thinking about that sort of thing now. Those are mostly implementation details, which will simply cause you confusion.
I suggest you start by writing what you want the language to do, and writing a grammar for it. When you have done that, you can consider writing a compiler. If your grammar is completely context‑free, you can use standard tools like lex and yacc or Antlr to create a compiler. Do you intend to compile the language to Java® bytecode or ordinary code?

Campbell wrote:you should not be thinking about that sort of thing now. Those are mostly implementation details, which will simply cause you confusion.

I suggest you start by writing a grammar for it.

In my opinion, when it comes to compiler development, those two suggestions are contradictory.

To write a grammar, you'll typically want to settle on a parser generator before you start, because otherwise you'll be spending a lot of time and effort rewriting your grammar later.

I don't have experience with JavaCC, but it appears to be a sensible choice. I can also vouch for ANTLR. Honestly, unless you're developing a production-ready compiler, the exact choice of parser generator doesn't matter that much. I do strongly recommend a parser generator that generates LL(k) or recursive descent parsers, as those are typically easier to use if you don't have a lot of experience with compiler development. Again, you should be fine with both JavaCC and ANTLR.

I discourage the use of yacc if this is your first compiler. It generates LALR parsers, and those are difficut to understand if you don't have experience wih them.

Daan Van Den Berg wrote:How can I do this?

One step at a time.

Start by writing a very basic grammar for the smallest legal compilation unit. See if you can get your parser generator to produce an output.

For instance, if I were to create a compiler for Java, I'd start by writing a grammar that accepts the following source file:
class Example {}
As Campbell already mentioned, it's very important to decide whether you want to compile your source files to Java, or to Java bytecode. It's probably easier to compile to Java when you're first starting out, but the choice mostly depends on what skills you want to practice with this project.

Try to compile your basic compilation unit to a .java or to a .class file. Then expand your project one feature at a time.

And if you're stuck, don't be afraid to ask questions.

Thank you very much for your helps.

My goal is to write an API in my own "X" language in the easiest way and develop a project using React.

Since it would take a long time to write all the functions myself, I was thinking of using java libraries directly, but I don't know how to do it.

I am a student who always develops software with high level languages, so I don't know much about this.

Should I write a compiler that translates the code I write in my language into Java or should I create a language where I write everything myself?

Alternatives...

One alternative is  to write a code generator based on some input other than a full programming language. As an example, I created a code generator that would query a database schema and build a set of classes based on the CRUD model with one subset for each table. The generated code has saved me many, many hours over the years and has resulted in very clean application code. The generated code is just Java and the API of the generated  code is how the application uses it.

Another approach is something similar to JSP where Java code and (in this case) JSP code is intermixed. A preprocessor is used to either pass the Java through to the generated file or expand the JSP into some logic implemented in Java and included in the generated file. This means you can use any library and incorporate any Java  syntax.

Both of these  approaches can be developed incrementally which will speed up development time.