6,782 reputation
33057
bio website youtube.com/…
location Jena, Germany
age 39
visits member for 3 years, 4 months
seen Jul 18 at 11:20

Drink milk, it is healthier then oil!

If you want to see how I see the Presenter first's implementation in Qt, take a look into my pet project.


Jul
18
reviewed Reviewed Practice programming guidance
Jul
18
revised Practice programming guidance
deleted 1 character in body
Jul
17
reviewed Reviewed Spring Controllers and Services
Jul
17
reviewed Reviewed Why is software OS specific?
Jul
17
reviewed Reviewed Partial sorting problem
Jul
16
comment Is it a good idea to “#define me (*this)”?
@Mehrdad Obviously, that is a personal preference. I surely hope your classes declarations and functions do not stretch over pages, so people wouldn't have to think long whether they access a local variable, or member variable.
Jul
16
reviewed Reject suggested edit on A newbie in python trying to learn
Jul
16
comment Is it a good idea to “#define me (*this)”?
@Mehrdad Are people still adding prefixes and suffixes to member variables? I thought that was "fixed" with books like Clean Code. this-> is as useful as auto in pre-c++11. In other words, it just increases code noise.
Jul
16
comment Is it a good idea to “#define me (*this)”?
@hildred I have nothing more to add to the point 3, except for the latest edit. As for the point 2, I feel sorry for whoever is unfortunate enough to have to read your code.
Jul
16
revised Is it a good idea to “#define me (*this)”?
added 1211 characters in body
Jul
16
revised Is it a good idea to “#define me (*this)”?
edited body
Jul
15
comment Is it a good idea to “#define me (*this)”?
@hildred See edits. Under "everybody" I meant people programming in c++ (obviously). The reference tells when this-> has to be used (some special case with templates, when a templated class inherits a class).
Jul
15
revised Is it a good idea to “#define me (*this)”?
added 17 characters in body
Jul
15
comment Is it a good idea to “#define me (*this)”?
@ThomasEding Please, next time provide a link to Q&A showing good uses of *this, as I am always eager to learn something new. And do not try to protect the nonsense in the question. Using this-> everywhere is just plain stupid
Jul
15
reviewed Reviewed Team workload algorithm
Jul
15
reviewed Approve suggested edit on Is it a good idea to “#define me (*this)”?
Jul
15
comment Does it make sense to use interfaces if you don't have polymorphism?
Prefer composition to inheritance... unless a class is used polymorphic.
Jul
15
awarded  Good Answer
Jul
15
comment Is it a good idea to “#define me (*this)”?
@MrLister My answer is "stupid defines are evil". The macro in the question is stupid to use, and as I showed, not needed at all. The code is good and even better without *this. and this->
Jul
15
awarded  Proofreader