<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Olib on The Last Psion</title><link>/tags/olib/</link><description>Recent content in Olib on The Last Psion</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Thu, 04 Jan 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/olib/index.xml" rel="self" type="application/rss+xml"/><item><title>Beginning OLIB: An entirely uneducated look at Psion's proprietary Object Oriented C</title><link>/posts/beginning-psion-olib-object-oriented-c/</link><pubDate>Thu, 04 Jan 2024 00:00:00 +0000</pubDate><guid>/posts/beginning-psion-olib-object-oriented-c/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Me:&lt;/strong&gt; I could do with a quick win to get me going again.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Also me:&lt;/strong&gt; I shall learn a proprietary object oriented dialect of C, where the only way to learn it is to plough through 1150 pages of documentation.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Psion doesn&amp;rsquo;t have a formal name for the object oriented version of C that it created for EPOC16.
I&amp;rsquo;ve been calling it &amp;ldquo;Psion OO C&amp;rdquo;, but the main library that it uses is called &lt;strong&gt;OLIB&lt;/strong&gt;, which contains the root class.
The others are:&lt;/p&gt;</description></item></channel></rss>