From: skaller <skaller@users.sourceforge.net>
To: Alan Falloon <Al.Falloon@synopsys.com>
Cc: David Teller <David.Teller@ens-lyon.org>, caml-list@inria.fr
Subject: Re: [Caml-list] what is high-level
Date: Sat, 05 Nov 2005 11:29:08 +1100 [thread overview]
Message-ID: <1131150548.31714.87.camel@rosella> (raw)
In-Reply-To: <436B871A.40906@synopsys.com>
On Fri, 2005-11-04 at 11:06 -0500, Alan Falloon wrote:
> typing" will make it clear in seconds.
>
> What we really need is a concept map from the popular languages (C, C++,
> Java, Python, Perl) to OCaml.
Felix. It isn't a concept, but an ML like language which binds
to C++.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2005-11-05 0:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 17:26 Wikipedia Jon Harrop
2005-11-03 19:24 ` [Caml-list] Wikipedia Gerd Stolpmann
2005-11-04 2:31 ` skaller
2005-11-04 13:46 ` [Caml-list] what is high-level (was: Wikipedia) Blue Prawn
2005-11-04 15:13 ` Brian Hurt
2005-11-04 15:28 ` David Teller
2005-11-04 16:02 ` skaller
2005-11-04 16:06 ` [Caml-list] what is high-level Alan Falloon
2005-11-04 16:10 ` William D. Neumann
2005-11-04 16:14 ` David Teller
2005-11-05 0:29 ` skaller [this message]
2005-11-05 22:05 ` Michael Walter
2005-11-06 14:28 ` skaller
2005-11-04 16:50 ` Matt Gushee
2005-11-03 19:30 ` [Caml-list] Wikipedia Kip Macy
2005-11-03 20:46 ` Matt Gushee
2005-11-03 21:08 ` Mike Lin
2005-11-03 21:16 ` Florian Weimer
2005-11-04 17:15 ` Thomas Fischbacher
2005-11-04 21:05 ` Alex Goldman
2005-11-04 21:53 ` Gerd Stolpmann
2005-11-04 22:24 ` Alex Goldman
2005-11-06 19:32 ` Thomas Fischbacher
2005-11-07 6:44 ` Tony Edgin
2005-11-07 12:23 ` Thomas Fischbacher
2005-11-07 12:55 ` skaller
2005-11-07 13:03 ` Thomas Fischbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1131150548.31714.87.camel@rosella \
--to=skaller@users.sourceforge.net \
--cc=Al.Falloon@synopsys.com \
--cc=David.Teller@ens-lyon.org \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox