<?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>Posts on Most Vexing Parse</title>
    <link>https://mostvexingparse.com/posts/</link>
    <description>Recent content in Posts on Most Vexing Parse</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 22 Oct 2021 10:10:17 -0400</lastBuildDate>
    <atom:link href="https://mostvexingparse.com/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction - what is the most vexing parse anyway?</title>
      <link>https://mostvexingparse.com/posts/intro/</link>
      <pubDate>Fri, 22 Oct 2021 10:10:17 -0400</pubDate>
      <guid>https://mostvexingparse.com/posts/intro/</guid>
      <description>&lt;p&gt;The title of this site refers to a phrase coined by Scott Meyers. The most vexing parse is a result of the ambiguity
of function declarations and variable definitions in C++, but I also think it&amp;rsquo;s a fun sequence of words.&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;ve probably run into this while trying to define a variable with a call to a default constructor. That happens
pretty frequently, so get in the habit of of doing so correctly: by omitting the empty parentheses, as in &lt;code&gt;string str&lt;/code&gt;
rather than &lt;code&gt;string str()&lt;/code&gt;. This is necessary because the latter is ambiguous:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
