<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>LASS</title>
	<link>http://lass.cocamware.com</link>
	<description>Library of Assembled Shared Sources, a product of Cocamware</description>
	<lastBuildDate>Sun, 22 Nov 2009 13:24:20 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>lass r1000</title>
		<description><![CDATA[We&#8217;re proud to announce our thousandth commit to the subversion repository.  More than enough reason for a party, and we are celebrating the event with a special release: lass-r1000.  
As an intermediate release, this is in fact version 1.3.8 of our trunk, and as such it is to be considered as a work [...]]]></description>
		<link>http://lass.cocamware.com/2009/07/14/lass-r1000/</link>
			</item>
	<item>
		<title>lass 1.2.1</title>
		<description><![CDATA[We&#8217;ve made a maintenance release of the 1.2 branch: lass-1.2.1.  It contains a few bug and build fixes discovered in the 1.2 branch:

Python:

CallMethod::set: make class of method a template parameter
RichCompare: const char* symbols to fix build warning
PyExportTraits: adding missing static specifier.


NumTraits:

default NumTraits is empty, so you get compiler errors for missing specialisations instead of [...]]]></description>
		<link>http://lass.cocamware.com/2009/03/10/lass-1-21/</link>
			</item>
	<item>
		<title>lass 1.2.0</title>
		<description><![CDATA[We&#8217;re proud to announce that we&#8217;ve made our second official release: lass-1.2.0.  It does not yet contain the file shuffling changes as previously explained.  As the trunk is undergoing a few larger (somewhat unstable) changes, this release is a snapshot of the last known stable state of the trunk before this work has [...]]]></description>
		<link>http://lass.cocamware.com/2009/02/02/lass-1-2-0/</link>
			</item>
	<item>
		<title>file shuffling</title>
		<description><![CDATA[Today, we&#8217;ve restructured the file hierarchy of lass a bit.  Here&#8217;s what has been done:

The directory src has been renamed to lass.  This allows you to include the headers from your working copy into other projects using the #include &#60;lass/foo/bar.h&#62; way.  It used to be that you either had to install lass, [...]]]></description>
		<link>http://lass.cocamware.com/2009/01/19/file-shuffling/</link>
			</item>
	<item>
		<title>LASS chooses CMake as build system</title>
		<description><![CDATA[We&#8217;re proud to announce that LASS now uses CMake as (meta) build system.  From a single set of cross-platform configuration files, it generates makefiles and workspaces, suitable for the native build tools available to the individual builder: GNU make, nmake, different flavours of Visual Studio, KDevelop, &#8230;  The only dependency introduced is an [...]]]></description>
		<link>http://lass.cocamware.com/2008/11/05/cmake-build-system/</link>
			</item>
	<item>
		<title>first official release</title>
		<description><![CDATA[We&#8217;re proud to announce we&#8217;ve made a first official source code release: lass-1.0.0.  Until now, we&#8217;ve never felt the need of explicit tarball releases as the CVS repository was a sufficient way of distributing the code.  But this has changed a little, so here it is.  Meanwhile, we&#8217;ll continue working on Lass [...]]]></description>
		<link>http://lass.cocamware.com/2008/07/18/first-official-release/</link>
			</item>
	<item>
		<title>migration to Subversion</title>
		<description><![CDATA[As the first news message since a very long time, we are pleased to announce that we have finally made the jump from CVS to Subversion (SVN).
]]></description>
		<link>http://lass.cocamware.com/2008/07/18/migration-to-subversion/</link>
			</item>
	<item>
		<title>revamping site &#8230;</title>
		<description><![CDATA[Welcome to LASS &#8230;
]]></description>
		<link>http://lass.cocamware.com/2006/01/25/revamping-site/</link>
			</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->