ftomassetti

I also loved that book! It is in my list of best books on building DSLs (https://tomassetti.me/domain-specific-languages#books)

That is also a good reason not to, but unfortunately that escape to most people

Thanks! Yes, it is a big pro the fact it supports so many languages, until you need to write semantic predicates at least

agreed! ANTLR 4 is so much better: writing rules with left recursion is much easier

One think I find lacking in books about building languages is a focus on tool. I am working on one (available for 0$ on leanpub: "How to create pragmatic, lightweight languages" https://leanpub.com/create_languages ) with the intention to focus more on building editors and simulator.

If you are interested in the subject you could take a look to my blog (https://tomassetti.me) I write 1-2 posts per week on building languages. Most of the time I talk about DSL.

SEEKING WORK - Remote or Lyon, France

I am an expert in language engineering: design DSLs, parsing, static analysis, IDE support are my specialty. ANTLR, Xtext and Jetbrains MPS are the tools I use the most.

I have a PhD, experience in 4 countries (Italy, Germany, Ireland and France), contributions to several open-source projects (e.g., JavaParser and WorldEngine) and an insane passion about software development.

Website: http://tomassetti.me

Github: https://github.com/ftomassetti/

Thanks for sharing it!

Just to add context: this is a post from a person involved in the project since 2004. It is a bit bitter but I found it interesting to read ("What happened to FFmpeg" by Kostya)

http://codecs.multimedia.cx/?p=339

I suggest take a look at a different point of view (https://blogs.gentoo.org/lu_zero/2015/02/20/demotivation-fud...)

This post is from someone involved in libav but it refers to the different public e-mails that were exchanged when the fork was originated and they document factually things (at least, as far as I can understand)

well, it is not that bad because as part of the tests it also parse all the code of Javaparser and spring-jdbc (by no means small projects). Parsing it is an expensive operation also because the Java grammar is quite ambiguous

Well, I am very interested in parsing and static analysis and if you idea and suggestions feel free to open as many tickets as you want on the project.

Yes, Hoogle is super cool, it would be definitely useful to have something like that.

I wrote in the past tools to manipulate ASTs of several languages but I have never looked in a Scala parser. Can you suggest one?

never saw this error but current version is 0.1.3-SNAPSHOT.

The instructions are probably confusing, I will fix them. You can run: lein jar java -jar target/effectivejava-0.1.3-SNAPSHOT.jar and then the options.

Thank you for reporting this!

Like many, I have fun using Clojure but during the day I have to pay bills by using Java :D

Jokes aside I think that Clojure is fantastic to manipulate data quickly. By the way this project is built on top of Javaparser (https://github.com/javaparser/javaparser) and that is written in Java.

Yes and no. If you consider this as a linter there are many others out there. Most of them in my opinion generate too much noise. I think that effectivejava is useful to explore your codebase, run a few queries and find out some facts about your code: how many utils classes do you have? How many methods are taking more than 5 parameters? You can run easily the queries on the whole project or just some packages and correct your aim as you find facts (for example, you may start asking how many methods take more than 5 parameters and realize they are 1000, then you want probably to start focusing on the methods taking more than 10 parameters. Or you can find that some classes with this problem are generated code and you do not want to consider them).

About the usage as a linter it tries to keep rules to a minimum of sensible rules, the ones explained in Effective Java. We chose them because they are rules well understood and accepted by the vast majority of developers so we hope to reduce the number of questionable findings returned to the user.

as a workaround we created the interactive mode in effectivejava. Also because parsing tons of files require a lot of work and you probably want avoid redoing it for every query

What about Sublime Text?