Reply to comment

Your reply

You need to sign up / log in to reply to this comment

Existing comment

I think 2) is a really bad idea.

The "old" way using constructors has the advantage, that one can be sure that all parameter were set after creation.

This is more like a parameter-less constructor and calling 'setProperty1()'.

In my opinion, this is bad code-style hidden behind code-sugar.

Thanks for commenting

Please remember:
Be polite, helpful and keep a positive attitude
Keep it short
Use examples
Review spelling and grammar

Please avoid:
Long texts
Code that is untested
Wall of text