On Tuesday 10 February 2015 12:37:28 Smith Martin wrote: > >For those guys, no amount of documentation will save them from writing > >bad code, so I don't think we should concern ourselves much with this > >case. > > > >I'm happy with the documentation if an educated developer reads it, and > >is able to make the correct decision on which container class to use.
Just a disclaimer: Martin omitted the attribution of the lines he quotes here. They are _not mine_. > You're sort of nullifying the concept of recommending best practices at > all. > > We won't be asking the developers to include basic CS concepts when > documenting a new class, if that's a worry. In this case, I asked for > clarification of some points, so I could add a recommendation to QMap > myself. > > I use QMap all the time, and almost certainly in situations where a vector > would be better. Why? Because it's dead simple and I need to get it > running now. I suppose we get used to doing the same thing the same way > and don't always pay attention to these details when a deadline is fast > approaching. It helps to be reminded of best practice tips from time to > time when checking a class I use out of habit. > > martin -- Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development