<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>std on nidomiro</title>
    <link>https://nidomiro.de/tags/std/</link>
    <description>Recent content in std on nidomiro</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Nov 2016 23:45:00 +0200</lastBuildDate><atom:link href="https://nidomiro.de/tags/std/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Should I use Qt containers or the std ones?</title>
      <link>https://nidomiro.de/2016/11/should-i-use-qt-containers-or-the-std-ones/</link>
      <pubDate>Wed, 02 Nov 2016 23:45:00 +0200</pubDate>
      
      <guid>https://nidomiro.de/2016/11/should-i-use-qt-containers-or-the-std-ones/</guid>
      <description>&lt;p&gt;If you come from plain vanilla C++, you only know the &lt;em&gt;C++ Standard Library&lt;/em&gt; with its containers like &lt;code&gt;std::vector&lt;/code&gt;. If you know how to use them, you can accomplish your tasks pretty fast. But if you’re coming from an other language, the naming might be a bit odd. The Qt containers offer both, C++ style and Java style naming of methods. So coming from an other language the Qt ones might be easier to use.&lt;/p&gt;
&lt;p&gt;</description>
    </item>
    
  </channel>
</rss>
