<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C on dev.endevour</title><link>https://devendevour.iankulin.com/tags/c/</link><description>Recent content in C on dev.endevour</description><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Tue, 16 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://devendevour.iankulin.com/tags/c/index.xml" rel="self" type="application/rss+xml"/><item><title>Protocols</title><link>https://devendevour.iankulin.com/protocols/</link><pubDate>Tue, 16 Aug 2022 00:00:00 +0000</pubDate><guid>https://devendevour.iankulin.com/protocols/</guid><description>&lt;p&gt;&lt;img src="https://devendevour.iankulin.com/images/protocoldroid-swe.jpg" alt="" class="img-responsive"&gt; &lt;/p&gt;
&lt;p&gt;The evolution of structs into class-like things that can hold properties &lt;em&gt;and&lt;/em&gt; methods in Swift raised in my mind &amp;ldquo;what about inheritance?&amp;rdquo; - but no: structs in Swift can not use inheritance.&lt;/p&gt;
&lt;p&gt;Swift classes implement inheritance, but only from one class; there&amp;rsquo;s no multiple inheritance. Protocols neatly address both these concerns to a large extent, but perhaps before we look at how they work, we should have a brief diversion into inheritance in C++.&lt;/p&gt;</description></item></channel></rss>