Comments on: QTL or STL? http://blog.codeimproved.net/2009/12/qtl-or-stl/ Fri, 24 Dec 2010 15:45:12 +0000 hourly 1 By: Rodney http://blog.codeimproved.net/2009/12/qtl-or-stl/comment-page-1/#comment-29 Rodney Wed, 14 Apr 2010 18:16:56 +0000 http://blog.codeimproved.net/?p=65#comment-29 Very helpful information, thanks! Very helpful information, thanks!

]]> By: Daniel Albuschat http://blog.codeimproved.net/2009/12/qtl-or-stl/comment-page-1/#comment-10 Daniel Albuschat Mon, 04 Jan 2010 14:39:46 +0000 http://blog.codeimproved.net/?p=65#comment-10 Regarding QString, it has another very important advantage: It is character-set-aware and even can transliterate between any supported character-set out of the box. That's something impossible with std::wstring, let alone std::string, but needed for most applications that handle external data in any way. Regarding QString, it has another very important advantage: It is character-set-aware and even can transliterate between any supported character-set out of the box. That’s something impossible with std::wstring, let alone std::string, but needed for most applications that handle external data in any way.

]]> By: raj http://blog.codeimproved.net/2009/12/qtl-or-stl/comment-page-1/#comment-9 raj Mon, 04 Jan 2010 02:43:03 +0000 http://blog.codeimproved.net/?p=65#comment-9 Check out this customization of allocator, makes initial allocation in stack, http://stackoverflow.com/questions/354442/looking-for-c-stl-like-vector-class-but-using-stack-storage/354481#354481 Check out this customization of allocator, makes initial allocation in stack, http://stackoverflow.com/questions/354442/looking-for-c-stl-like-vector-class-but-using-stack-storage/354481#354481

]]> By: rpg http://blog.codeimproved.net/2009/12/qtl-or-stl/comment-page-1/#comment-8 rpg Sun, 03 Jan 2010 19:18:43 +0000 http://blog.codeimproved.net/?p=65#comment-8 Re: customizable allocator I agree that most people will never write their own allocator since the default one will be sufficient for them. However, there are special cases when using a custom allocator would significantly improve performance. e.g: Using a pool allocator when working with lots of small objects. I assume that Trolltech didn't want to incur the costs of allocator customizations. So far this has not bothered me, and I would just use a STL container for that special case. Re: customizable allocator

I agree that most people will never write their own allocator since the default one will be sufficient for them.

However, there are special cases when using a custom allocator would significantly improve performance. e.g: Using a pool allocator when working with lots of small objects.

I assume that Trolltech didn’t want to incur the costs of allocator customizations. So far this has not bothered me, and I would just use a STL container for that special case.

]]>