<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for panta</title>
    <link>http://www.advogato.org/person/panta/</link>
    <description>Advogato blog for panta</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Fri, 10 Oct 2008 18:42:57 GMT</pubDate>
    <item>
      <pubDate>Fri, 17 Nov 2000 01:10:18 GMT</pubDate>
      <title>17 Nov 2000</title>
      <link>http://www.advogato.org/person/panta/diary.html?start=2</link>
      <guid>http://www.advogato.org/person/panta/diary.html?start=2</guid>
      <description>I've radically changed the command line parsing library API.
At the same time I've added some features and I've packaged
the whole thing. I've also written some documentation.
</description>
    </item>
    <item>
      <pubDate>Wed, 15 Nov 2000 20:17:22 GMT</pubDate>
      <title>15 Nov 2000</title>
      <link>http://www.advogato.org/person/panta/diary.html?start=1</link>
      <guid>http://www.advogato.org/person/panta/diary.html?start=1</guid>
      <description>&lt;p&gt;Today I had a good deal of boring things to do, and I
wont talk about them :)
&lt;p&gt;In the remaining time, I've started to put together (and
almost finished) a small C library to parse the command line
(similar in spirit to getopt() and getopt_long()). Why ?
Because I don't like getopt() and getopt_long(), and also
because having my own small lib, I can integrate it in
elastiC with not too much hassle, and avoid depending on
undependable libc features. Stay tuned.
</description>
    </item>
    <item>
      <pubDate>Tue, 14 Nov 2000 18:29:19 GMT</pubDate>
      <title>14 Nov 2000</title>
      <link>http://www.advogato.org/person/panta/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/panta/diary.html?start=0</guid>
      <description>&lt;p&gt;Prepared a benchmark to test elastiC implementation of
hash tables.
&lt;p&gt;Very long meeting, lunch.
&lt;p&gt;Then I returned to hack on elastiC. I'm trying to
understand why the hell loading a shared module makes
&lt;tt&gt;dlopen()&lt;/tt&gt; to complain about an undefined symbol
(symbol that
is in the elastiC core) &lt;i&gt;but only when elastiC is
configured with &lt;tt&gt;--enable-static&lt;/tt&gt; and
&lt;tt&gt;--disable-shared&lt;/tt&gt;&lt;/i&gt;. libtool bug ? Boh, we'll
see...
</description>
    </item>
  </channel>
</rss>
