Ever consider Project Lombok?

[TheLQ]

As I'm starting to learn PMS's API more and look at more code I'm noticing a few POJO's. One thing that I think might be helpful is Project Lombok ( http://projectlombok.org/ ). This allows you to specify getters, setters, tostring, hascode, etc with just an annotation. This does help reduce code clutter since you don't have a wall of getters and setters between major parts of your code. You could also start to phase out calling fields by their direct field names, which is generally bad practice.

If nobody wants to implement it I would be willing to help out when I finish my VLC project. Once again though I'm simply wondering if PMS devs are open to the idea.

[chocolateboy]

This allows you to specify getters, setters, tostring, hascode, etc with just an annotation.

These are trivial to generate with an IDE. There are many things that should be improved in PMS. I wouldn't say this is one of them.

[TheLQ]

This allows you to specify getters, setters, tostring, hascode, etc with just an annotation.

These are trivial to generate with an IDE. There are many things that should be improved in PMS. I wouldn't say this is one of them.

Its an improvement though with little to no effort. See http://projectlombok.org/features/Data.html for example. I just mainly use it to reduce code clutter. 100 lines of getters and setters tends to bury real code

[chocolateboy]

I've seen it before (albeit many years ago and not in connection with PMS). IIRC, the main issue was debugging - which its code generation made much harder. Has that been solved?

More importantly, I'd rather have verbose and idiotic Java code that spells things out than magical Java code that doesn't. The lack of "cleverness" is precisely what makes it so easy to understand and hack on.

[taconaut]

I like the idea.
Coming from c# that's one of the things I've never liked with java. Declaring a simple public property with getter and stter resumes to this

Code: Select all

public int MyNumber { get; set; }

[Raptor399]

I feel old; I can't read the Lombok code.

The old code may be bulky, but it spells it all out and I don't have to be aware of what magic the annotations invoke under water (it may be gone from sight, but it still is there).

[TheLQ]

In all honsetly the code was unstable in earlier versions but now it is extremely stable. Many large projects use it without any problems. And in the end if you can't get it to work or need the full code you can run delombok and get pure non-magic java code to work with

[happy.neko]

This allows you to specify getters, setters, tostring, hascode, etc with just an annotation.

Another option is to use proper IDE.

[chocolateboy]

Another option is to use proper IDE.

Another option is to read the thread:

These are trivial to generate with an IDE.