Network objects (was RE: deriving (...))

Mon, 18 Nov 2002 18:02:59 +1100

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C28ED0.877E0540
Content-Type: text/plain;
	charset="iso-8859-1"

> BTW, those typed returns on sockets that Shawn mentioned sounded
> interesting. IIRC Modula-3 also had some approach to worrying about data
> exchange between older and newer versions of the same program.

Modula-3 (actually the Network Objects library) used subtyping to handle
this.  Successive versions of an interface are declared as subtypes of the
previous version, and the type system will resolve a network object binding
to the appropriate version.  

Hard to see how this could be done in a purely functional setting.

robin

------_=_NextPart_001_01C28ED0.877E0540
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Network objects (was RE: deriving (...))</TITLE>
</HEAD>
<BODY>
<BR>

&gt; BTW, those typed returns on sockets that Shawn =
mentioned sounded
 &gt; interesting. IIRC Modula-3 also had some =
approach to worrying about data
 &gt; exchange between older and newer versions of =
the same program.

<P><FONT SIZE=3D2>Modula-3 (actually the Network Objects library) used =
subtyping to handle this.&nbsp; Successive versions of an interface are =
declared as subtypes of the previous version, and the type system will =
resolve a network object binding to the appropriate version.&nbsp; =
</FONT></P>

<P><FONT SIZE=3D2>Hard to see how this could be done in a purely =
functional setting.</FONT>
</P>

<P><FONT SIZE=3D2>robin</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C28ED0.877E0540--