<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Library AutoiNEATialization</title>
	<atom:link href="http://pocoproject.org/blog/?feed=rss2&#038;p=741" rel="self" type="application/rss+xml" />
	<link>http://pocoproject.org/blog/?p=741</link>
	<description>News and discussion for the POCO Community</description>
	<lastBuildDate>Thu, 09 May 2013 12:05:16 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: alex</title>
		<link>http://pocoproject.org/blog/?p=741&#038;cpage=1#comment-1911</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Mon, 15 Apr 2013 07:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://pocoproject.org/blog/?p=741#comment-1911</guid>
		<description>Explicit calls are obviously available through initialization object, eg:

SQLite::Connector::registerConnector();

Calling initialization repeatedly is what I was trying to avoid in the first place because that is something that is needed exactly once at startup and should not be called repeatedly forever.</description>
		<content:encoded><![CDATA[<p>Explicit calls are obviously available through initialization object, eg:</p>
<p>SQLite::Connector::registerConnector();</p>
<p>Calling initialization repeatedly is what I was trying to avoid in the first place because that is something that is needed exactly once at startup and should not be called repeatedly forever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dshor</title>
		<link>http://pocoproject.org/blog/?p=741&#038;cpage=1#comment-1870</link>
		<dc:creator>dshor</dc:creator>
		<pubDate>Thu, 21 Mar 2013 12:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://pocoproject.org/blog/?p=741#comment-1870</guid>
		<description>just make sure its not prone to static initializer fiasco. some user library that uses one of those POCO libraries uses the same static init pattern, may be initialized before them.  at least make some explicit POCO_init available for them to use.  but the library may not be aware of the need for explicit init, until some static initializer fiasco symptoms begin.  singleton initializers are the best way to go, basically the (1) option, call initialization (repeatedly)</description>
		<content:encoded><![CDATA[<p>just make sure its not prone to static initializer fiasco. some user library that uses one of those POCO libraries uses the same static init pattern, may be initialized before them.  at least make some explicit POCO_init available for them to use.  but the library may not be aware of the need for explicit init, until some static initializer fiasco symptoms begin.  singleton initializers are the best way to go, basically the (1) option, call initialization (repeatedly)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
