<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:osnews="http://osnews.com/rss2#">
	<channel>
		<title>OSNews: </title>
		<link>http://www.osnews.com/story/21332/New_Features_in_Glibc_2_10</link>
		<description>Exploring the Future of Computing</description>
		<language>en-us</language>
		<copyright>Copyright 2001-2009, David Adams</copyright>
		<webMaster>adam+nospam@osnews.com</webMaster>
		<lastBuildDate>Mon, 07 Dec 2009 01:54:33 GMT</lastBuildDate>
		<image>
			<url>http://www.osnews.com/images/osnews.gif</url>
			<title>OSNews.com</title>
			<link>http://www.osnews.com</link>
		</image>
		<item>
			<title>Comment by Bending Unit</title>
			<link>http://osnews.com/thread?359260</link>
			<guid isPermaLink="true">http://osnews.com/thread?359260</guid>
			<description>Ulrich Drepper</description>
			<pubDate>Sat, 18 Apr 2009 15:31:00 GMT</pubDate>
			<author>donotreply@osnews.com (Bending Unit)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>Automatic use of optimized function</title>
			<link>http://osnews.com/thread?359265</link>
			<guid isPermaLink="true">http://osnews.com/thread?359265</guid>
			<description>What I found even more interesting is an automatic use of optimized function that the new glibc features.</description>
			<pubDate>Sat, 18 Apr 2009 15:47:00 GMT</pubDate>
			<author>donotreply@osnews.com (cromo)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>C++ 201x ?? </title>
			<link>http://osnews.com/thread?359291</link>
			<guid isPermaLink="true">http://osnews.com/thread?359291</guid>
			<description>I thought it was 200x.<br />
<br />
It seems to still not implemented and we will see them speaking about 203x</description>
			<pubDate>Sat, 18 Apr 2009 18:24:00 GMT</pubDate>
			<author>donotreply@osnews.com (boulabiar)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>libc/xml</title>
			<link>http://osnews.com/thread?359317</link>
			<guid isPermaLink="true">http://osnews.com/thread?359317</guid>
			<description>the malloc_info function returns an xml string? mixing up xml with the libc library seems to me a bad idea.</description>
			<pubDate>Sat, 18 Apr 2009 23:51:00 GMT</pubDate>
			<author>donotreply@osnews.com (TObYv)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: libc/xml</title>
			<link>http://osnews.com/thread?359354</link>
			<guid isPermaLink="true">http://osnews.com/thread?359354</guid>
			<description>Fully agree.<br />
Using normal flat structures would have been far more useful.<br />
<br />
- Gilboa</description>
			<pubDate>Sun, 19 Apr 2009 10:57:00 GMT</pubDate>
			<author>donotreply@osnews.com (gilboa)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE[2]: libc/xml</title>
			<link>http://osnews.com/thread?359359</link>
			<guid isPermaLink="true">http://osnews.com/thread?359359</guid>
			<description>Or providing versioned reader functions that can query the otherwise opaque structure returned from mallinfo().  It's not a hard problem to solve.  Looks like Ulrich just wanted to throw up his hands and let someone else deal with it.  Fortunately, it's not something I really care about, so it's no big deal either way for me.</description>
			<pubDate>Sun, 19 Apr 2009 14:53:00 GMT</pubDate>
			<author>donotreply@osnews.com (siride)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: libc/xml</title>
			<link>http://osnews.com/thread?359443</link>
			<guid isPermaLink="true">http://osnews.com/thread?359443</guid>
			<description>No kidding. XML as an integral part of Glibc? Please save us from this lunacy.</description>
			<pubDate>Mon, 20 Apr 2009 10:48:00 GMT</pubDate>
			<author>donotreply@osnews.com (Vanders)</author>
			<category>Comments</category>
		</item>
	</channel>
</rss>
