caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mattias Waldau <mattias.waldau@abc.se>
To: caml-list@inria.fr
Subject: re: [Caml-list] Large projects in OCaml
Date: Tue, 25 May 2004 09:26:56 +0200	[thread overview]
Message-ID: <40B2F540.9070702@abc.se> (raw)

ExcelEverywhere, which converts Excel spreadsheets into web pages where 
JavaScript does all the calculation is written in Ocaml.

The program consists of 40,000 lines of Ocaml, a 10,000 lines of 
JavaScript and Excel VBA.

We do no GUI in Ocaml, everything is done in VBA. The ocaml-part is just 
a native code compiled win32-executable.

We had very few problems with bugs with the ocaml-implementation, and 
always found simple workarounds.

Development is done on cygwin and linux, since we really like 
ocamldebug, the debugger that can execute backwards.

One big problem is that many of the good ocaml libraries are GPL, and 
cannot be used by ISV. For example, we had to implement our own XML-library.

If your datastructures are large, I would not recommend delivering 
byte-compiled code. It is noticable slower and easily runs out of memory.

If you use resonable datastructure, speed will not be a problem.

Good luck,

Mattias





-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2004-05-25  7:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25  7:26 Mattias Waldau [this message]
2004-05-25 19:07 ` Richard Jones
2004-05-25 19:54   ` Evan Martin
2004-05-26  6:57   ` skaller
2004-05-26  8:09     ` Richard Jones
  -- strict thread matches above, loose matches on Subject: below --
2004-05-19 17:24 ramu ramamurthy
2004-05-19 21:33 ` Jon Harrop
2004-05-19 23:04   ` David J. Trombley
2004-05-20 16:31   ` Eric Stokes
2004-05-20 17:37     ` Jon Harrop
2004-05-20 20:30       ` Eric Stokes
2004-05-20 21:04         ` Jon Harrop
2004-05-20 21:41           ` Eric Stokes
2004-05-21 11:28             ` Jon Harrop
2004-05-21 12:49               ` Ville-Pertti Keinonen
2004-05-21 16:27                 ` Jon Harrop
2004-05-24  3:07               ` Jacques GARRIGUE
2004-05-24  5:20                 ` skaller
2004-05-24 12:14                   ` Jacques GARRIGUE
2004-05-24 13:54                     ` skaller
2004-05-24 14:20                       ` Xavier Leroy
2004-05-24 16:48                         ` Alex Baretta
2004-05-24 17:38                           ` brogoff
2004-05-25  5:25                           ` Alan Schmitt
2004-05-24 19:24                         ` skaller
2004-05-24 19:52                           ` Brandon J. Van Every
2004-05-24 14:20                       ` Daniel Bünzli
2004-05-24 19:34                         ` skaller
2004-05-24 16:49                       ` james woodyatt
2004-05-19 21:38 ` Richard Jones
2004-05-20  8:46   ` skaller
2004-05-20 13:10     ` Jon Harrop
2004-05-20 16:23       ` skaller
2004-05-20  6:35 ` David Monniaux
2004-05-20  7:17   ` Dustin Sallings

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=40B2F540.9070702@abc.se \
    --to=mattias.waldau@abc.se \
    --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;
as well as URLs for NNTP newsgroup(s).