<?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: Namespaces, Again</title>
	<atom:link href="http://pocoproject.org/blog/?feed=rss2&#038;p=14" rel="self" type="application/rss+xml" />
	<link>http://pocoproject.org/blog/?p=14</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: Gypsy1</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-43</link>
		<dc:creator>Gypsy1</dc:creator>
		<pubDate>Wed, 16 Aug 2006 22:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-43</guid>
		<description>This is just a response to comment # 2.

  The reason for &#039;Poco&#039; and not &#039;poco&#039; is naming convention. I would guess the developer(s) are trying to differentiate the class name from regular variable names. It&#039;s common pratice once you get into it.</description>
		<content:encoded><![CDATA[<p>This is just a response to comment # 2.</p>
<p>  The reason for &#8216;Poco&#8217; and not &#8216;poco&#8217; is naming convention. I would guess the developer(s) are trying to differentiate the class name from regular variable names. It&#8217;s common pratice once you get into it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: guenter</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-42</link>
		<dc:creator>guenter</dc:creator>
		<pubDate>Wed, 16 Aug 2006 14:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-42</guid>
		<description>We&#039;ll handle this on a case-by-case basis, which might include maintaining two parallel versions for some time...

Experience with our own codebase shows that the change can be made with a few global search/replace operations and is a matter of a few hours at most, so I think it&#039;s not that much of a problem.</description>
		<content:encoded><![CDATA[<p>We&#8217;ll handle this on a case-by-case basis, which might include maintaining two parallel versions for some time&#8230;</p>
<p>Experience with our own codebase shows that the change can be made with a few global search/replace operations and is a matter of a few hours at most, so I think it&#8217;s not that much of a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-41</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Wed, 16 Aug 2006 13:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-41</guid>
		<description>Did Poco have commercial customers before going open source?
My initial impression was that this was a stable commercial library that was already widely used that has now been open sourced.
With changes as significant as you have just made what happnes to exisiting code?
I have no issue with the change since I am just beginnig to check the library out but am wondering how long time users will react to these changes.

F.</description>
		<content:encoded><![CDATA[<p>Did Poco have commercial customers before going open source?<br />
My initial impression was that this was a stable commercial library that was already widely used that has now been open sourced.<br />
With changes as significant as you have just made what happnes to exisiting code?<br />
I have no issue with the change since I am just beginnig to check the library out but am wondering how long time users will react to these changes.</p>
<p>F.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: guenter</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-40</link>
		<dc:creator>guenter</dc:creator>
		<pubDate>Wed, 16 Aug 2006 05:45:24 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-40</guid>
		<description>I have switched all of Poco, as well as some of our proprietary libs to the new namespace and headers scheme. The transition has been quite smooth - global search/replace is all that&#039;s needed, and I really like the result so far. After some tests on more platforms I will release a new preview of 1.2 later today (or tomorrow, latest).

To sum it up:
&lt;ul&gt;
	&lt;li&gt;The Foundation namespace is now just Poco.&lt;/li&gt;
	&lt;li&gt;XML, Util and Net have become Poco::XML, Poco::Util and Poco::Net.&lt;/li&gt;
	&lt;li&gt;#includes are now in the form #include &quot;Poco/Foundation.h&quot; for Foundation headers and #include &quot;Poco/XML/XML.h&quot; for other libs.&lt;/li&gt;
&lt;/ul&gt;</description>
		<content:encoded><![CDATA[<p>I have switched all of Poco, as well as some of our proprietary libs to the new namespace and headers scheme. The transition has been quite smooth &#8211; global search/replace is all that&#8217;s needed, and I really like the result so far. After some tests on more platforms I will release a new preview of 1.2 later today (or tomorrow, latest).</p>
<p>To sum it up:</p>
<ul>
<li>The Foundation namespace is now just Poco.</li>
<li>XML, Util and Net have become Poco::XML, Poco::Util and Poco::Net.</li>
<li>#includes are now in the form #include &#8220;Poco/Foundation.h&#8221; for Foundation headers and #include &#8220;Poco/XML/XML.h&#8221; for other libs.</li>
</ul>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-39</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Tue, 15 Aug 2006 19:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-39</guid>
		<description>I&#039;m OK with it (especially with dropping Foundation).</description>
		<content:encoded><![CDATA[<p>I&#8217;m OK with it (especially with dropping Foundation).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-38</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Tue, 15 Aug 2006 17:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-38</guid>
		<description>I have just began looking at Poco.
Foundation is kind of verbose. I was thinking why not &#039;base&#039;.
And &#039;poco&#039; instead of &#039;Poco&#039;</description>
		<content:encoded><![CDATA[<p>I have just began looking at Poco.<br />
Foundation is kind of verbose. I was thinking why not &#8216;base&#8217;.<br />
And &#8216;poco&#8217; instead of &#8216;Poco&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Marlow</title>
		<link>http://pocoproject.org/blog/?p=14&#038;cpage=1#comment-37</link>
		<dc:creator>Andrew Marlow</dc:creator>
		<pubDate>Tue, 15 Aug 2006 15:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=14#comment-37</guid>
		<description>These changes sound excellent to me. :-)</description>
		<content:encoded><![CDATA[<p>These changes sound excellent to me. <img src='http://pocoproject.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
