aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2000-November/000073.html
blob: 3f993b8019f0e6c897228cb0f513aa9759b4ec92 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [offtopic] distributed scripting language (was: Re: [Nel] Distributed server algo)</TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:David.Mentre%40irisa.fr">
   <LINK REL="Previous"  HREF="000072.html">
   <LINK REL="Next" HREF="000067.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[offtopic] distributed scripting language (was: Re: [Nel] Distributed server algo)</H1>
    <B>David Mentre</B> 
    <A HREF="mailto:David.Mentre%40irisa.fr"
       TITLE="[offtopic] distributed scripting language (was: Re: [Nel] Distributed server algo)">David.Mentre@irisa.fr</A><BR>
    <I>30 Nov 2000 08:59:54 +0100</I>
    <P><UL>
        <LI> Previous message: <A HREF="000072.html">[Nel] Distributed server algo</A></li>
        <LI> Next message: <A HREF="000067.html">[Nel] pointers on documentation?</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#73">[ date ]</a>
              <a href="thread.html#73">[ thread ]</a>
              <a href="subject.html#73">[ subject ]</a>
              <a href="author.html#73">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Thierry Mallard &lt;<A HREF="mailto:thierry@mallard.com">thierry@mallard.com</A>&gt; writes:

&gt;<i> I'm now trying to implement a STAGE server (see projet Worldforge[1]),
</I>&gt;<i> with the help of Mickael Remond, using Erlang[2], a functionnal
</I>&gt;<i> language which does has nice features about distribution.
</I>
You could also have a look at Objective Caml[1]. It is a functionnal
language (ML style with type inference for those interested) but with
modules and object oriented capabilities. It has not pre-build
distributed facilities but toolkits have been built on it, like
Ensemble[2].

On Erlang, one thing to notice is that reliability is in charge of the
programmer. But maybe your are involved in some other projects using
Erlang. ;)

&gt;<i>  Maybe that could be worth a look, although I'm still not sure an
</I>&gt;<i> interpreted language is really usable for something like NeL or
</I>&gt;<i> STAGE...
</I>
OCaml can be compiled in both bytecode and native code for about any
platform (from ARM to Alpha through x86 [2b]). And people have made
hacks to dynamically load bytecode and native code into
programs[3]. Also notice that bytecode is portable across platforms.

Sorry if it is a bit of topic, but I could not resist for this blatant
advertising. ;) And maybe NeL will have more that just Python support...

Best regards,
d.

[1] <A HREF="http://caml.inria.fr/">http://caml.inria.fr/</A>
[2] <A HREF="http://www.cs.cornell.edu/Info/Projects/Ensemble/index.html">http://www.cs.cornell.edu/Info/Projects/Ensemble/index.html</A>
[2b] <A HREF="http://caml.inria.fr/ocaml/portability.html">http://caml.inria.fr/ocaml/portability.html</A>
[3] <A HREF="http://caml.inria.fr/archives/200011/msg00180.html">http://caml.inria.fr/archives/200011/msg00180.html</A>
-- 
 <A HREF="mailto:David.Mentre@irisa.fr">David.Mentre@irisa.fr</A> -- <A HREF="http://www.irisa.fr/prive/dmentre/">http://www.irisa.fr/prive/dmentre/</A>
 Opinions expressed here are only mine.

</pre>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI> Previous message: <A HREF="000072.html">[Nel] Distributed server algo</A></li>
	<LI> Next message: <A HREF="000067.html">[Nel] pointers on documentation?</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#73">[ date ]</a>
              <a href="thread.html#73">[ thread ]</a>
              <a href="subject.html#73">[ subject ]</a>
              <a href="author.html#73">[ author ]</a>
         </LI>
       </UL>
</body></html>