<?xml version="1.0"?>
<rss version="2.0">

<channel>
	<title>OCamlcore Planet</title>
	<link>http://planet.ocamlcore.org</link>
	<language>en</language>
	<description>OCamlcore Planet - http://planet.ocamlcore.org</description>

<item>
	<title>FP-Sydney: FP-Syd #22.</title>
	<guid isPermaLink="false">http://www.mega-nerd.com/erikd/Blog/FP-Syd/FP-Syd/fp-syd-22</guid>
	<link>http://www.mega-nerd.com/erikd/Blog/FP-Syd/fp-syd-22.html</link>
	<description>&lt;p&gt;
On Thursday February 25th we held the first meeting for 2010 of the Sydney
Functional Programming group.
The meeting was held at Google's Sydney offices and we had 17 people show up
to hear our two presenters.
&lt;/p&gt;

&lt;p&gt;
First up we had your correspondent (Erik de Castro Lopo), giving a
presentation titled
	&lt;a href=&quot;http://groups.google.com/group/fp-syd/web/hacking-ddc.pdf&quot;&gt;
	&quot;Hacking DDC&quot;&lt;/a&gt;
on my bug fixing work on Ben Lippmeier's 
	&lt;a href=&quot;http://www.haskell.org/haskellwiki/DDC&quot;&gt;
	DDC compiler&lt;/a&gt;.
I explained a little about what DDC and Disciple were; a Haskell like language
with some interesting extensions to the type system.
I then suggested that anyone curious as to why these extensions were interesting
should read the first chapter of Ben's PhD thesis
	&lt;a href=&quot;http://cs.anu.edu.au/~Ben.Lippmeier/project/thesis/thesis-lippmeier-sub.pdf&quot;&gt;
	&quot;Type Inference and Optimisation for an Impure World&quot;&lt;/a&gt;.
I then went on how using Darcs for the revision control made it easy to use one
branch per bug or feature I'm working on,  specifically, it allowed me to work
on one until I got stuck and then move on to another without the debugging of
the first interfering with the second.
&lt;/p&gt;

&lt;p&gt;
Our second presenter for the evening was Tim Docker who gave us an explanation
of a Domain Specific Language (DSL) for handling dates in financial systems.
Code written in his DSL looked a lot like Ocaml, but the implementation was in
C++.
&lt;/p&gt;

&lt;p&gt;
A big thanks to Tim for presenting and Google for providing the meeting venue
and the snacks.
&lt;/p&gt;</description>
	<pubDate>Sat, 13 Mar 2010 00:57:00 +0000</pubDate>
</item>
<item>
	<title>OCamlCore Forge News: CCSS 1.1 released</title>
	<guid isPermaLink="true">http://forge.ocamlcore.org/forum/forum.php?forum_id=561</guid>
	<link>http://forge.ocamlcore.org/forum/forum.php?forum_id=561</link>
	<description>This version adds support for unit conversion.  This feature is off by default; please provide command line option '--convert' (short version '-c') to activate it.</description>
	<pubDate>Fri, 12 Mar 2010 04:38:10 +0000</pubDate>
</item>
<item>
	<title>Erik de Castro Lopo: Intel Embedded Graphics Driver Fail.</title>
	<guid isPermaLink="true">http://www.mega-nerd.com/erikd/Blog/CodeHacking/Embedded/intel_graphics_fail.html</guid>
	<link>http://www.mega-nerd.com/erikd/Blog/CodeHacking/Embedded/intel_graphics_fail.html</link>
	<description>&lt;p&gt;
In my day job I do Linux embedded work and as people in the embedded world know,
Linux is a pretty commonly used embedded OS.
Today I was evaluating a new board and found it had an Intel graphics chip that
was not properly detected by Ubuntu 9.10.
The ever trusty &lt;tt&gt;&lt;b&gt;lspci&lt;/b&gt;&lt;/tt&gt; said this:
&lt;/p&gt;

&lt;pre class=&quot;code&quot;&gt;  00:02.0 VGA compatible controller: Intel Corporation System Controller Hub
        	(SCH Poulsbo) Graphics Controller (rev 07)

&lt;/pre&gt;

&lt;p&gt;
We all know that Intel employs a bunch of well known
	&lt;a href=&quot;http://www.x.org/wiki/&quot;&gt;
	Xorg&lt;/a&gt;
developers, so this shouldn't be a problem, right?
&lt;/p&gt;

&lt;p&gt;
Unfortunately, it is a problem.
Intel's offering for this chipset is the
	&lt;a href=&quot;http://edc.intel.com/Software/Downloads/IEGD/&quot;&gt;
	Intel® Embedded Graphics Drivers&lt;/a&gt;
web page where they offer a 124 megabyte download (registration required).
After registration you get to choose which driver pack you want and which OS
you are downloading it for.
Ubuntu was not on the list and neither was Debian.
I chose Fedora 10 (released in 2008) as that was the most recent one.
&lt;/p&gt;

&lt;p&gt;
Now, you can image my surprise when the driver download for Fedora Linux
contained just four files:
&lt;/p&gt;

&lt;pre class=&quot;code&quot;&gt;  Archive:  /tmp/IEGD_10_3_GOLD.zip
      testing: UsersGuide_10_3_1525.pdf   OK
      testing: IEGD_10_3_GOLD_1525.exe    OK
      testing: IEGD_SU_10_3_GOLD.pdf      OK
      testing: RELNOTES_10_3_1525.txt     OK
  No errors detected in compressed data of /tmp/IEGD_10_3_GOLD.zip.

&lt;/pre&gt;

&lt;p&gt;
Yep, thats right, the driver download for Fedora Linux contains two PDF files,
a text file and an executable installer for &lt;i&gt;Windows&lt;/i&gt;.
&lt;/p&gt;

&lt;p&gt;
Being the curious (and paranoid) type I decided to explore this further,
by running the installer under
	&lt;a href=&quot;http://www.winehq.com/&quot;&gt;
	WINE&lt;/a&gt;
in a
	&lt;a href=&quot;http://en.wikipedia.org/wiki/Chroot&quot;&gt;
	chroot&lt;/a&gt;.
After the installer you get left with several metric craploads of Java Jar
files, and another windows executable &lt;tt&gt;&lt;b&gt;iegd-ced.exe&lt;/b&gt;&lt;/tt&gt; that
supposedly configures this nightmare.
I ran it (again, under WINE in a chroot) but it didn't seem to do anything
sensible or worthwhile so I looked around amongst the other installed files
and found &lt;tt&gt;&lt;b&gt;IEGD_10_3_Linux.tgz&lt;/b&gt;&lt;/tt&gt;.
&lt;/p&gt;

&lt;p&gt;
Inside that tarball there are a bunch of Xorg library binaries (for several
different versions of Xorg), a large chunk of source code that gets compiled
into the Linux kernel and even better yet, a couple of Microsoft Visual
Studio project files.
WTF?
&lt;/p&gt;

&lt;p&gt;
Unbe-fscking-lievable.
Needless to say, I will avoid any hardware which uses this chipset and
any other hardware that requires binary only kernel blobs packaged this
badly.
Doing so makes my life easier.
&lt;/p&gt;

&lt;p&gt;
The people at Intel who thought this was a good idea must have their own
personal mother-lode of stupid.
&lt;/p&gt;</description>
	<pubDate>Thu, 11 Mar 2010 10:00:28 +0000</pubDate>
</item>
<item>
	<title>The Caml Humps: CCSS 1.0</title>
	<guid isPermaLink="true">http://caml.inria.fr/cgi-bin/hump.cgi?contrib=722</guid>
	<link>http://caml.inria.fr/cgi-bin/hump.cgi?contrib=722</link>
	<description>CCSS is a preprocessor/pretty-printer for CSS (Cascading Style Sheets). It extends the CSS language with support for declaration of variables and basic arithmetic operations (addition, subtraction, multiplication, division). The programme is supposed to be used as a filter: it reads the CSS source from stdin and outputs its result on stdout.</description>
	<pubDate>Thu, 11 Mar 2010 07:01:13 +0000</pubDate>
</item>
<item>
	<title>The Caml Humps: OCaml Batteries Included 1.1.0</title>
	<guid isPermaLink="true">http://caml.inria.fr/cgi-bin/hump.cgi?contrib=659</guid>
	<link>http://caml.inria.fr/cgi-bin/hump.cgi?contrib=659</link>
	<description>Batteries Included is a candidate standard
development platform for OCaml.</description>
	<pubDate>Thu, 11 Mar 2010 06:44:49 +0000</pubDate>
</item>
<item>
	<title>OCamlCore Forge News: CCSS 1.0 released</title>
	<guid isPermaLink="true">http://forge.ocamlcore.org/forum/forum.php?forum_id=560</guid>
	<link>http://forge.ocamlcore.org/forum/forum.php?forum_id=560</link>
	<description>CCSS is a preprocessor for CSS, extending the language with arithmetic operations and the possibility to declare and use variables. This is the first public release of the project.</description>
	<pubDate>Thu, 11 Mar 2010 04:48:16 +0000</pubDate>
</item>
<item>
	<title>Sylvain Le Gall: LLVM, OCaml and Debian</title>
	<guid isPermaLink="false">tag:le-gall.net,2010-03-10:/sylvain+violaine/blog/55</guid>
	<link>http://le-gall.net/sylvain+violaine/blog/index.php?2010/03/10/55-llvm-ocaml-and-debian</link>
	<description>&lt;p&gt;I hope some people from the OCaml community will enjoy this changelog, extracted from llvm 2.6-7, which has just been uploaded:&lt;/p&gt;

&lt;pre&gt;  [ Arthur Loiret ]
   
  [...]

  [ Sylvain Le Gall ]
  * Build a libllvm-ocaml-dev package, which contains the OCaml binding:
    Closes: #568556.
    - debian/debhelper.in/libllvm-ocaml-dev.{dirs,doc-base,install,META}: Add.
    - debian/control.in/source: Build-Depends on ocaml-nox (&amp;gt;= 3.11.2),
      ocaml-best-compilers | ocaml-nox, dh-ocaml (&amp;gt;= 0.9.1).
    - debian/packages.d/llvm.mk:
      + (llvm_packages): Add libllvm-ocaml-dev.
      + (libllvm-ocaml-dev_extra_binary): Define, install META file.
    - debian/rules.d/binary.mk: Add dh_installdirs and dh_ocaml.
    - debian/rules.d/vars.mk:
      + include /usr/share/ocaml/ocamlvars.mk.
      + Configure with --with-ocaml-libdir=$(OCAML_STDLIB_DIR)/llvm.
  * debian/rules.d/build.mk: Fix symlinks pointing to the $DESTDIR.&lt;/pre&gt;


&lt;p&gt;In other words: LLVM is now built with its OCaml bindings and a META file for findlib. It will take some days before reaching every architectures, but hopefully it will be in Squeeze (next Debian stable release).&lt;/p&gt;


&lt;p&gt;Thanks to Arthur Loiret for the quick upload.&lt;/p&gt;</description>
	<pubDate>Wed, 10 Mar 2010 18:07:37 +0000</pubDate>
</item>
<item>
	<title>Caml Weekly News: Caml Weekly News, 09 Mar 2010</title>
	<guid isPermaLink="true">http://alan.petitepomme.net/cwn/2010.03.09.html</guid>
	<link>http://alan.petitepomme.net/cwn/2010.03.09.html</link>
	<description>gc overhead / MetaOCaml lives! / Encoding an extensible parse tree and subtyping within OCaml / NaCl/OCaml (OCaml as a client-side web programming language) / Commercial Users of Functional Programming - call for participation / Other Caml News</description>
	<pubDate>Tue, 09 Mar 2010 12:00:00 +0000</pubDate>
</item>
<item>
	<title>Romain Beauxis: Liquidsoap-full 0.9.2-2 and ocaml-cry 0.1.2</title>
	<guid isPermaLink="true">http://blog.rastageeks.org/spip.php?article58</guid>
	<link>http://blog.rastageeks.org/spip.php?article58</link>
	<description>&lt;div class=&quot;rss_texte&quot;&gt;&lt;p&gt;An issue with the new ocaml-cry module that replaces the shout library has been recently discovered.&lt;/p&gt; &lt;p&gt;This issue was related to the data sent to the icecast server and could result in a higher load and loss of data when sending data to the server.&lt;/p&gt; &lt;p&gt;We have released a new version of ocaml-cry that fixes this issue, numbered 0.1.2.&lt;/p&gt; &lt;p&gt;We have also released a new liquidsoap-full tarball, numbered 0.9.2-2 and now available in the download section on &lt;a href=&quot;http://sourceforge.net/projects/savonet/files/&quot; class=&quot;spip_out&quot;&gt;sourceforge.net&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Additionally, our custom stable packages have been rebuild against this new version, both for the i386 and the amd64 architecture.&lt;/p&gt; &lt;p&gt;The package available in Debian sid/unstable is now built against the fixed ocaml-cry as well.&lt;/p&gt; &lt;p&gt;We recommend that any user that uses liquidsoap 0.9.2 updates its liquidsoap to make sure it uses ocaml-cry 0.1.2.&lt;/p&gt; &lt;p&gt;Please note that ocaml modules are not dynamically loaded, so you need to rebuild liquidsoap against the new ocaml-cry if you are building from source.&lt;/p&gt;&lt;/div&gt;</description>
	<pubDate>Mon, 08 Mar 2010 23:13:43 +0000</pubDate>
</item>
<item>
	<title>Stefano Zacchiroli: ocaml batteries included 1.1.0 is in debian now</title>
	<guid isPermaLink="true">http://upsilon.cc/~zack/blog/posts/2010/03/ocaml_batteries_included_1.1.0_is_in_debian_now/</guid>
	<link>http://upsilon.cc/~zack/blog/posts/2010/03/ocaml_batteries_included_1.1.0_is_in_debian_now/</link>
	<description>&lt;h1&gt;OCaml Batteries Included 1.1.0 has arrived in Debian&lt;/h1&gt;
&lt;p&gt;I've just uploaded the &lt;strong&gt;Debian package of &lt;a href=&quot;https://forge.ocamlcore.org/forum/forum.php?forum_id=552&quot;&gt;OCaml
Batteries Included 1.1.0&lt;/a&gt;&lt;/strong&gt; to the Debian unstable
archive; hopefully, it will quickly enter testing to be released
with the next Debian stable release. This is the first release in
Debian of the &quot;new generation&quot; of Batteries Included, which has
followed a strict diet, and now has &lt;a href=&quot;http://camomile.sourceforge.net/&quot;&gt;Camomile&lt;/a&gt; as its only
external dependency.&lt;/p&gt;
&lt;p&gt;It took me a while to package it due to an intertwining
transition to OCaml 3.11.2 (during which we have fleshed out the
last remaining few bits of transition to &lt;a href=&quot;http://upsilon.cc/~zack/tags/ocaml/../../blog/posts/2009/11/Enforcing_type-safe_linking_using_package_dependencies/&quot;&gt;
our new dependency system&lt;/a&gt;). Also, I had to fix some typical
build issue with upstream, which kindly coordinated with me to have
the fixes included in 1.1.0.&lt;/p&gt;
&lt;p&gt;So go, enjoy Batteries 1.1.0, and let me know your feedback:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;    # apt-get install ocaml-batteries-included
&lt;/code&gt;
&lt;/pre&gt;
&lt;p&gt;&lt;small&gt;(check that it will install 1.1.0 though, it might take a
few days to hit your favorite architecture and mirror)&lt;/small&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Tip:&lt;/strong&gt; starting from this version you will need
the following to use Batteries in place of the legacy standard
library in your sources:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;    open Batteries_uni
&lt;/code&gt;
&lt;/pre&gt;
&lt;p&gt;for multi-threaded programs you should rather use &lt;code&gt;open
Batteries&lt;/code&gt;. Check the &lt;code&gt;FAQ&lt;/code&gt; file installed under
&lt;code&gt;/usr/share/doc/libbatteries-ocaml-dev/&lt;/code&gt; for more quick
start information.&lt;/p&gt;</description>
	<pubDate>Sat, 06 Mar 2010 15:39:15 +0000</pubDate>
</item>

</channel>
</rss>
