<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19120"></HEAD>
<BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px"
id=MailContainerBody leftMargin=0 topMargin=0 bgColor=#ffffff
CanvasTabStop="true" name="Compose message area">
<DIV><FONT size=2 face=Arial>
<DIV><FONT size=2 face=Arial>I recently came across an article that might
interest the community:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial><A
title="http://nativesystems.inf.ethz.ch/pub/Main/FelixFriedrichPublications/UnifiedStaticDynamicLoading.pdf
CTRL + Click to follow link"
href="http://nativesystems.inf.ethz.ch/pub/Main/FelixFriedrichPublications/UnifiedStaticDynamicLoading.pdf">A
Compiler-Supported Unification of Static and Dynamic Loading</A></FONT></DIV>
<DIV><FONT size=2 face=Arial>by Felix Friedrich and Florian Negele</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>It is about platform-independent linking and
loading of modules.</FONT></DIV>
<DIV><FONT size=2 face=Arial>The mechanism is explained in context of
the A2 (ex-Bluebottle)</FONT></DIV>
<DIV><FONT size=2 face=Arial>OS and the Active Oberon language, but it is
easily portable to</FONT></DIV>
<DIV><FONT size=2 face=Arial>other programming environments and
languages.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Its adoption, at the cost of rewriting the backend
and parts of</FONT></DIV>
<DIV><FONT size=2 face=Arial>m3core, would </FONT><FONT size=2
face=Arial>significantly simplify the maintenance of </FONT><FONT size=2
face=Arial>M3 and</FONT></DIV>
<DIV><FONT size=2 face=Arial>also render it </FONT><FONT size=2
face=Arial>independent from proprietary
tools.</FONT></DIV></FONT></DIV></BODY></HTML>