From: "Arnaud SAHUGUET" <sahuguet@lucent.com>
To: "MONIN Jean-Francois FTRD/DTL/LAN"
<jeanfrancois.monin@rd.francetelecom.com>
Cc: "Xavier Leroy" <xavier.leroy@inria.fr>,
"Yurii A. Rashkovskii" <yrashk@openeas.org>,
"Ohad Rodeh" <ORODEH@il.ibm.com>, <caml-list@inria.fr>
Subject: Re: [Caml-list] OcamlSpread 0.0.1 released
Date: Fri, 20 Sep 2002 14:57:55 -0400 [thread overview]
Message-ID: <02bf01c260d7$b355b950$141919ac@bl.belllabs.com> (raw)
In-Reply-To: <15755.18764.944202.516163@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Re: [Caml-list] OcamlSpread 0.0.1 releasedImplementing crypto packages is a real pain.
I wrote an implementation of DES in Java in 1996. Absolutely not interesting for me.
For this kind of stuff, I think writing an oCaml wrapper on top of C library is better.
>
More seriously, perhaps, a well-known source of flaws is complexity.
Expressing algorithms in Ocaml is often (much) less complex than
in C...
-- That's probably true for public key cryptography. For symmetric key crypto and hash function, the algorithms are not elegant.
In companies, there is always the dilemma: make vs buy.
I think the oCaml community should think about "re-implement vs wrap". I don't think the real value of oCaml programming sits at the level of the OS or the low-level libraries.
Arnaud
[-- Attachment #2: Type: text/html, Size: 1739 bytes --]
next prev parent reply other threads:[~2002-09-20 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 16:14 MONIN Jean-Francois FTRD/DTL/LAN
2002-09-20 16:18 ` Re[2]: " Yurii A. Rashkovskii
2002-09-20 18:57 ` Arnaud SAHUGUET [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 20:49 Re[6]: " Ohad Rodeh
2002-09-18 22:44 ` Blair Zajac
2002-09-18 16:56 Re[4]: " Ohad Rodeh
2002-09-18 17:59 ` Re[6]: " Yurii A. Rashkovskii
2002-09-20 13:15 ` Xavier Leroy
2002-09-20 14:45 ` Arnaud SAHUGUET
2002-09-17 20:06 Ohad Rodeh
2002-09-17 11:15 Yurii A. Rashkovskii
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='02bf01c260d7$b355b950$141919ac@bl.belllabs.com' \
--to=sahuguet@lucent.com \
--cc=ORODEH@il.ibm.com \
--cc=caml-list@inria.fr \
--cc=jeanfrancois.monin@rd.francetelecom.com \
--cc=xavier.leroy@inria.fr \
--cc=yrashk@openeas.org \
/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