From: Yoann Padioleau <padator@wanadoo.fr>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: "OCaml List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] designing Ocaml programs with a graphical modeling language ?
Date: Thu, 25 Jan 2007 15:42:58 +0100 [thread overview]
Message-ID: <87tzyfdv65.fsf@wanadoo.fr> (raw)
In-Reply-To: <200701251221.10701.jon@ffconsultancy.com> (Jon Harrop's message of "Thu, 25 Jan 2007 12:21:10 +0000")
Jon Harrop <jon@ffconsultancy.com> writes:
> 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 know "Visual Haskell", maybe it can helps
http://ptolemy.eecs.berkeley.edu/~johnr/papers/visual.html
>
> 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.
You can run your program with profiling on and then use the callgraph
generated by gprof and pass it into dot.
> 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
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2007-01-25 14:44 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
2007-01-25 14:42 ` Yoann Padioleau [this message]
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=87tzyfdv65.fsf@wanadoo.fr \
--to=padator@wanadoo.fr \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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).