<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Kommentare zu: New C++ Database Library in the Make</title>
	<link>http://blogs.newphoria.de/2008/11/01/new-c-database-library-in-the-make/</link>
	<description>Newphoria Project News</description>
	<pubDate>Sun, 20 May 2012 20:48:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>Von: ekkehard</title>
		<link>http://blogs.newphoria.de/2008/11/01/new-c-database-library-in-the-make/#comment-4</link>
		<author>ekkehard</author>
		<pubDate>Sat, 15 Nov 2008 14:34:00 +0000</pubDate>
		<guid>http://blogs.newphoria.de/2008/11/01/new-c-database-library-in-the-make/#comment-4</guid>
		<description>BTW, in the meantime, I have used a more traditional solution to templates. The support of "export" has been removed. Instead, the template implementation is included only where needed, and there's exactly one module for every template instance. In all other cases, templates are just declared, not implemented, when #included. This achieves the greatest possible portability.

Use of namespaces is optional. Compilers without "stdint.h" and "stdbool.h" are supported.</description>
		<content:encoded><![CDATA[<p>BTW, in the meantime, I have used a more traditional solution to templates. The support of &#8220;export&#8221; has been removed. Instead, the template implementation is included only where needed, and there&#8217;s exactly one module for every template instance. In all other cases, templates are just declared, not implemented, when #included. This achieves the greatest possible portability.</p>
<p>Use of namespaces is optional. Compilers without &#8220;stdint.h&#8221; and &#8220;stdbool.h&#8221; are supported.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: ekkehard</title>
		<link>http://blogs.newphoria.de/2008/11/01/new-c-database-library-in-the-make/#comment-3</link>
		<author>ekkehard</author>
		<pubDate>Fri, 14 Nov 2008 15:38:06 +0000</pubDate>
		<guid>http://blogs.newphoria.de/2008/11/01/new-c-database-library-in-the-make/#comment-3</guid>
		<description>ADB is making good progress, I have finished a lot of components and the basic (on-disk) memory management is already working. The resulting database files are entirely architecture-independent. :)

64-bit arithmetic is required, however. But this is no problem on any current platform. 

Data type support for records include 8 to 64 bit integers, signed and unsigned, and multibyte and wide character strings. Floating-point is not inherently supported, because it is not necessary (fixed-point arithmetic does a better job for business applications). There is also the problem that representing floating-point in a platform-independent manner is somewhat difficult, character strings being arguably the best form. Wide characters are only supported as 16-bit and 32-bit representations.</description>
		<content:encoded><![CDATA[<p>ADB is making good progress, I have finished a lot of components and the basic (on-disk) memory management is already working. The resulting database files are entirely architecture-independent. <img src='http://blogs.newphoria.de/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>64-bit arithmetic is required, however. But this is no problem on any current platform. </p>
<p>Data type support for records include 8 to 64 bit integers, signed and unsigned, and multibyte and wide character strings. Floating-point is not inherently supported, because it is not necessary (fixed-point arithmetic does a better job for business applications). There is also the problem that representing floating-point in a platform-independent manner is somewhat difficult, character strings being arguably the best form. Wide characters are only supported as 16-bit and 32-bit representations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

