<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>My desperate life quest for efficiency</title>
	<link>http://efiquest.org</link>
	<description>(mostly in programming and *nix administration)</description>
	<pubDate>Wed, 08 Sep 2010 13:51:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>
	<language>en</language>
			<item>
		<title>Zveriki game is now available at odnoklassniki.ru</title>
		<link>http://efiquest.org/2010-09-06/46/</link>
		<comments>http://efiquest.org/2010-09-06/46/#comments</comments>
		<pubDate>Mon, 06 Sep 2010 12:47:15 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[zveriki]]></category>

		<category><![CDATA[gamedev]]></category>

		<guid isPermaLink="false">http://efiquest.org/2010-09-06/46/</guid>
		<description><![CDATA[ The game I&#8217;m currently working on  is now officially available on Russian social service odnoklassniki.ru(quite popular in Russia and somewhat similar to linkedin). Hope our servers can handle the load 
]]></description>
		<wfw:commentRss>http://efiquest.org/2010-09-06/46/feed/</wfw:commentRss>
		</item>
		<item>
		<title>gcc precompiled headers weird behaviour with -c option</title>
		<link>http://efiquest.org/2010-03-28/45/</link>
		<comments>http://efiquest.org/2010-03-28/45/#comments</comments>
		<pubDate>Sat, 27 Mar 2010 21:50:42 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[pch]]></category>

		<category><![CDATA[gcc]]></category>

		<category><![CDATA[c++]]></category>

		<guid isPermaLink="false">http://efiquest.org/2010-03-28/45/</guid>
		<description><![CDATA[Short story
Use -fpch-preprocess option alongside with -c option in order to make precompiled headers work properly.
Update: I asked the same question on the gcc help mailing list and Ian Lance Taylor explained this strange behavior by my usage of distcc/ccache. These tools first preprocess the source that&#8217;s why this options is required.
Long story
I&#8217;m using gcc-4.4.1 [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2010-03-28/45/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Mercurial file conflicts resolution similar to Subversion behavior</title>
		<link>http://efiquest.org/2010-01-08/43/</link>
		<comments>http://efiquest.org/2010-01-08/43/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 19:21:38 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[mercurial]]></category>

		<category><![CDATA[subversion]]></category>

		<guid isPermaLink="false">http://efiquest.org/2010-01-08/43/</guid>
		<description><![CDATA[For the impatient
Ok, here is what you have to do on your Ubuntu box:

$ sudo apt-get install rcs
$ vim ~/.hgrc

&#8230; and put the following lines somewhere into your ~/.hgrc

[merge-tools]
merge.priority = 100

The full story
As an active user of the Mercurial version control system I&#8217;ve been struggling for quite some time with its merging facilities. Actually all [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2010-01-08/43/feed/</wfw:commentRss>
		</item>
		<item>
		<title>glibc-2.7 makecontext issues on x86_64</title>
		<link>http://efiquest.org/2009-12-28/42/</link>
		<comments>http://efiquest.org/2009-12-28/42/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 10:31:40 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[x86_64]]></category>

		<category><![CDATA[glibc]]></category>

		<category><![CDATA[gcc]]></category>

		<category><![CDATA[*nix]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-12-28/42/</guid>
		<description><![CDATA[Looks like passing 64 bit values(e.g pointers) into makecontext is not working properly on x86_64. We are using makecontext for coroutines implementation and its proper working is vital for us.
I&#8217;ve been struggling with this bug for a couple of days and have finally found a solution for it. Actually the solution is trivial it was [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-12-28/42/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Redirect build errors into vim</title>
		<link>http://efiquest.org/2009-12-10/41/</link>
		<comments>http://efiquest.org/2009-12-10/41/#comments</comments>
		<pubDate>Wed, 09 Dec 2009 20:53:42 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[bash]]></category>

		<category><![CDATA[automation]]></category>

		<category><![CDATA[vim]]></category>

		<category><![CDATA[*nix]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-12-10/41/</guid>
		<description><![CDATA[Here is a small bash function which wraps the executed command in the shell and redirects all build errors right into vim. In vim you can jump between errors using standard :cn,:cp commands(as well as view them all using :cope).

function vimize &#40;&#41; 
&#123; 
  local file=/tmp/vimize.errors
  if &#91; &#34;$1&#34; != &#34;&#34; &#93; ; [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-12-10/41/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Using boost::threadpool with boost::future</title>
		<link>http://efiquest.org/2009-12-10/40/</link>
		<comments>http://efiquest.org/2009-12-10/40/#comments</comments>
		<pubDate>Wed, 09 Dec 2009 20:18:18 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[async]]></category>

		<category><![CDATA[multicore]]></category>

		<category><![CDATA[boost]]></category>

		<category><![CDATA[c++]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-12-10/40/</guid>
		<description><![CDATA[Here is a small c++ function which allows you to submit async jobs into the thread pool and track their execution status using the conception of futures:

#include &#34;boost/threadpool.hpp&#34;
#include &#34;boost/future.hpp&#34;
#include &#34;boost/utility/result_of.hpp&#34;
#include &#34;boost/shared_ptr.hpp&#34;
&#160;
template&#60;typename Thp, typename Func&#62;
boost::shared_future&#60; typename boost::result_of&#60;Func&#40;&#41;&#62;::type &#62;
submit_job&#40;Thp&#38; thp, Func f&#41;
&#123;
  typedef typename boost::result_of&#60;Func&#40;&#41;&#62;::type result;
  typedef boost::packaged_task&#60;result&#62; packaged_task;
  typedef boost::shared_ptr&#60;boost::packaged_task&#60;result&#62; &#62; packaged_task_ptr;
&#160;
  [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-12-10/40/feed/</wfw:commentRss>
		</item>
		<item>
		<title>dctl Xtra 0.1 released</title>
		<link>http://efiquest.org/2009-09-14/39/</link>
		<comments>http://efiquest.org/2009-09-14/39/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 10:01:32 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[automation]]></category>

		<category><![CDATA[xtra]]></category>

		<category><![CDATA[director]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-09-14/39/</guid>
		<description><![CDATA[Hi folks!
We at my company created a simple Xtra(called dctl which means Director ConTroL) which allows us to control the Adobe Director via the network socket.  The idea is very simple: the Xtra listens on some port using Multiuser facility and allows to run a set of predefined tasks(which can be very easily extended, [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-09-14/39/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Zveriki is the prize-winner of &#8220;The best online game&#8221; KRI2009-Award</title>
		<link>http://efiquest.org/2009-05-19/37/</link>
		<comments>http://efiquest.org/2009-05-19/37/#comments</comments>
		<pubDate>Tue, 19 May 2009 05:25:29 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[gamedev]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-05-19/37/</guid>
		<description><![CDATA[Hurray! Our project Zveriki got &#8220;The best online game&#8221; award at KRI-2009(analogue of GDC in Russia)  The game is still in active development and we provided demo access only to the press and members of the jury. Earlier we hoped the game would be launched in November 2008, however the World Crisis changed our [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-05-19/37/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Best git-svn practices?</title>
		<link>http://efiquest.org/2009-02-21/33/</link>
		<comments>http://efiquest.org/2009-02-21/33/#comments</comments>
		<pubDate>Sat, 21 Feb 2009 08:00:46 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[svn]]></category>

		<category><![CDATA[git]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-02-21/33/</guid>
		<description><![CDATA[I wonder if there are any &#8220;best git-svn practices&#8221;? Particularly for the following scenario:
1) There is a common svn repository
2) There are several developers who track/sync this common svn repo with their own local git repos using git-svn bridge(via git svn rebase/dcommit)
3) From time to time these developers using git need to share their changes [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-02-21/33/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Processing results of vimgrep in vim</title>
		<link>http://efiquest.org/2009-02-19/32/</link>
		<comments>http://efiquest.org/2009-02-19/32/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 19:11:43 +0000</pubDate>
		<dc:creator>pachanga</dc:creator>
		
		<category><![CDATA[vim]]></category>

		<guid isPermaLink="false">http://efiquest.org/2009-02-19/32/</guid>
		<description><![CDATA[What I&#8217;ve been really missing in vim is a general mechanism of applying any arbitrary processing to the results of :vim[grep] command. What I usually did was to record a macro and apply it manually(using :cp) to every entry in a quickfix window - believe me, that&#8217;s very boring. Big thanks goes to Ben Schmidt [...]]]></description>
		<wfw:commentRss>http://efiquest.org/2009-02-19/32/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
