<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Serializing on Christian Gmeiner</title>
    <link>https://playground.christian-gmeiner.info/tags/serializing/</link>
    <description>Recent content in Serializing on Christian Gmeiner</description>
    <image>
      <title>Christian Gmeiner</title>
      <url>https://playground.christian-gmeiner.info/papermod-cover.png</url>
      <link>https://playground.christian-gmeiner.info/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 May 2015 19:42:28 +0000</lastBuildDate>
    <atom:link href="https://playground.christian-gmeiner.info/tags/serializing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>QMetaEnum: Serializing C&#43;&#43; Enums</title>
      <link>https://playground.christian-gmeiner.info/2015-05-25-qmetaenum-serializing-c-enums/</link>
      <pubDate>Mon, 25 May 2015 19:42:28 +0000</pubDate>
      <guid>https://playground.christian-gmeiner.info/2015-05-25-qmetaenum-serializing-c-enums/</guid>
      <description>&lt;p&gt;I think that almost every C++ programmer looked into a nice and easy way to do C++ Enum serialization. You may want to store the Enum value in a human readable format (json, ini, ..) and later you may also want to read back the value into the object.&lt;/p&gt;
&lt;p&gt;You have here two way how to archive your goal. Use simple int values to represent the Enum value or use Strings. The big advantage with strings it that you do not have to lookup what the meaning of value 4 is, but you can name the value with a String.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
