Once I was put in charge of a project where an "engineer" had replaced (inherited) all the Qt Q* classes used in the project to classes that did not have a 'Q' as a first letter. No other changes. And yes, that "engineer" was a contractor.
> Sent: Tuesday, July 21, 2015 at 1:03 PM > From: "Gunnar Roth" <gunnar.r...@gmx.de> > To: "Guido Seifert" <warg...@gmx.de> > Cc: interest@qt-project.org > Subject: Re: [Interest] Need argumentative help..... giving qobject > copy/assignment constructor and put it in qlist/qmap > > Well here people who write that kind of code become project lead or product > managers , so they can no longer harm the code ;-) > > > Am 21.07.2015 um 18:34 schrieb Guido Seifert <warg...@gmx.de>: > > > > > > > >> > > > >> hi, > >> > >> i wonder why you just don't store QObject* in the lists? > >> moving from objects to pointers should be "just" fleißarbeit ;) > > > > > > I 'inherited' the code. And yes, this is exactly what I do now... though it > > is not 'just' fleißarbeit. To reintroduce proper memory management > > proved to be a real challenge. :-/ > > > > As I said earlier... the programmers here are not bad, but I get the > > feeling that the sprints might be a bit too demanding. Shortcuts are taken, > > which no experienced programmer would take voluntarily if he has a choice. > > :-( > > > > Guido > > _______________________________________________ > > Interest mailing list > > Interest@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/interest > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
