From: Jon Harrop <jon@ffconsultancy.com>
To: "OCaml List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] designing Ocaml programs with a graphical modeling language ?
Date: Thu, 25 Jan 2007 12:21:10 +0000 [thread overview]
Message-ID: <200701251221.10701.jon@ffconsultancy.com> (raw)
In-Reply-To: <45B88884.4060300@atosorigin.com>
On Thursday 25 January 2007 10:37, Stéphane DUPRAT wrote:
> ...
> As for me, I think that designing with a graphical modeling language
> could be profitable.
I see. While I haven't seen any graphical modelling languages for FPLs, there
are tools to automate the visualisation of dependencies. I found them quite
useful (and fun!).
I'd like some tools to plot OCaml call graphs and so on. Also to find
exceptions that can propagate to the top level (I never got ocamlexn to
work).
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2007-01-25 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 10:36 Stéphane DUPRAT
[not found] ` <200701241901.37939.jon@ffconsultancy.com>
2007-01-25 10:37 ` [Caml-list] " Stéphane DUPRAT
2007-01-25 12:21 ` Jon Harrop [this message]
2007-01-25 14:42 ` Yoann Padioleau
2007-01-25 14:18 ` skaller
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=200701251221.10701.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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