<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Anatoliy Belsky - Python</title>
    <link>http://belsky.info/</link>
    <description>That's what I'm thinking ...  </description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.5.5 - http://www.s9y.org/</generator>
    
    

<item>
    <title>A tool for quick c one liners</title>
    <link>http://belsky.info/archives/33-A-tool-for-quick-c-one-liners.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>Python</category>
    
    <comments>http://belsky.info/archives/33-A-tool-for-quick-c-one-liners.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=33</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=33</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    There is always something to try out when writing c programs. Sometimes you just want to know if a small piece of code works as expected without having to recompile the whole project. I used to write small programs for this, just like&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;&lt;b&gt;C:&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;pre class=&quot;c&quot; style=&quot;color: #000066; border: 1px solid #d0d0d0; background-color: #f0f0f0;padding-left: 3px;&quot;&gt;&lt;span style=&quot;color: #339933;&quot;&gt;#include &amp;lt;stdio.h&amp;gt;&lt;/span&gt;
&amp;#160;
&lt;span style=&quot;color: #993333;&quot;&gt;int&lt;/span&gt; main&lt;span style=&quot;color: #66cc66;&quot;&gt;&amp;#40;&lt;/span&gt;&lt;span style=&quot;color: #993333;&quot;&gt;void&lt;/span&gt;&lt;span style=&quot;color: #66cc66;&quot;&gt;&amp;#41;&lt;/span&gt;
&lt;span style=&quot;color: #66cc66;&quot;&gt;&amp;#123;&lt;/span&gt;
    &lt;a style=&quot;color: #000060;&quot; href=&quot;http://www.opengroup.org/onlinepubs/009695399/functions/printf.html&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;printf&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;color: #66cc66;&quot;&gt;&amp;#40;&lt;/span&gt;&lt;span style=&quot;color: #ff0000;&quot;&gt;&amp;quot;%c&lt;span style=&quot;color: #000099; font-weight: bold;&quot;&gt;\n&lt;/span&gt;&amp;quot;&lt;/span&gt;, &lt;span style=&quot;color: #cc66cc;&quot;&gt;127&lt;/span&gt;&lt;span style=&quot;color: #66cc66;&quot;&gt;&amp;#41;&lt;/span&gt;;
&amp;#160;
    &lt;span style=&quot;color: #b1b100;&quot;&gt;return&lt;/span&gt; &lt;span style=&quot;color: #cc66cc;&quot;&gt;0&lt;/span&gt;;
&lt;span style=&quot;color: #66cc66;&quot;&gt;&amp;#125;&lt;/span&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;
&lt;br /&gt;
But the more you program c, the more pieces of code you possibly want to try out. And writing all that wrapping stuff around the snippet you actually want to check isn&#039;t really productive. Therefore I came to the idea of a small program which would straight forward compile and run a piece of c code.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/33-A-tool-for-quick-c-one-liners.html#extended&quot;&gt;Continue reading &quot;A tool for quick c one liners&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 06 May 2012 23:38:00 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/33-guid.html</guid>
    
</item>
<item>
    <title>Functions vs. inline code</title>
    <link>http://belsky.info/archives/21-Functions-vs.-inline-code.html</link>
            <category>Perl</category>
            <category>PHP5</category>
            <category>Python</category>
    
    <comments>http://belsky.info/archives/21-Functions-vs.-inline-code.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=21</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=21</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Recently I had a little discussion about our style guide with one of the co-workers. And the matter was concerning the line length. Most default is to limit the line length with 79-85 characters - because of terminals, printing etc. But an other question took my head in the middle of the conversation: limiting the line length would mean for example to encapsulate deep included blocks of the code into functions - sounds not bad, but ... &lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/21-Functions-vs.-inline-code.html#extended&quot;&gt;Continue reading &quot;Functions vs. inline code&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 22 Jun 2008 16:56:22 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/21-guid.html</guid>
    
</item>
<item>
    <title>Don't underestimate SQL</title>
    <link>http://belsky.info/archives/18-Dont-underestimate-SQL.html</link>
            <category>Bash</category>
            <category>PostgreSQL</category>
            <category>Python</category>
    
    <comments>http://belsky.info/archives/18-Dont-underestimate-SQL.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=18</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=18</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Hi there.&lt;br /&gt;
&lt;br /&gt;
The things I wanna to talk about today are - relational databases building. Particularly I would discuss such the attainments of relational sql as join and subselect. For my experiment I&#039;ll take PostgreSQL and Python.&lt;br /&gt;
&lt;br /&gt;
So, lets start:&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;&lt;b&gt;BASH:&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;pre class=&quot;bash&quot; style=&quot;color: #000066; border: 1px solid #d0d0d0; background-color: #f0f0f0;padding-left: 3px;&quot;&gt;user@host~$ &lt;span style=&quot;color: #c20cb9; font-weight: bold;&quot;&gt;su&lt;/span&gt; postgres
postgres@host~$ createuser -P &lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;test&lt;/span&gt;
Enter password &lt;span style=&quot;color: #000000; font-weight: bold;&quot;&gt;for&lt;/span&gt; new role:
Enter it again:
Shall the new role be a superuser? &lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;&amp;#40;&lt;/span&gt;y/n&lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;&amp;#41;&lt;/span&gt; n
Shall the new role be allowed to create &lt;span style=&quot;color: #c20cb9; font-weight: bold;&quot;&gt;more&lt;/span&gt; new roles? &lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;&amp;#40;&lt;/span&gt;y/n&lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;&amp;#41;&lt;/span&gt; n
postgres@host~$ createdb &lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;test&lt;/span&gt;
postgres@host~$ &lt;span style=&quot;color: #7a0874; font-weight: bold;&quot;&gt;exit&lt;/span&gt;&lt;/pre&gt;&lt;/div&gt; &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/18-Dont-underestimate-SQL.html#extended&quot;&gt;Continue reading &quot;Don&#039;t underestimate SQL&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 27 Apr 2008 21:37:00 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/18-guid.html</guid>
    
</item>

</channel>
</rss>
