From: "Jocelyn Sérot" <jserot@lasmea.univ-bpclermont.fr>
To: oliver@first.in-berlin.de (Oliver Bandel)
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] graphical notation/representation of functional programs?
Date: Fri, 21 Feb 2003 10:04:48 +0100 [thread overview]
Message-ID: <8726DA8D-457B-11D7-8129-0003934491C2@lasmea.univ-bpclermont.fr> (raw)
In-Reply-To: <20030220164049.GA762@first.in-berlin.de>
Le jeudi, 20 fév 2003, à 17:40 Europe/Paris, Oliver Bandel a écrit :
> Hello,
>
>
> when using graphical representations like in
> "The Craft of Functional Programming", so that
> a function is a box with in- and output, then
> it's a convenient way of looking at functional
> programs.
>
> Is that technique of overview more elaborated
> used by other people?
>
> Shouldn't it possible to have a graphical notation
> for FP, like a functional aequivalent of the notation,
> that is used in the OO-programmers world, where
> classes and methods and attributes and so on
> are presentated in a graphical manner?
>
> Are there papers on that topic?
> Or is functional programming in higher spheres
> done comepletely an algebraic form 8lambda calculus)?
>
> Ciao,
> Oliver
Here are two papers i am aware of (sorry, i don't have the urls at hand
now, but a search
on the web should give them to you) :
* J.ohn Reekie. "Visual Haskell : a first attempt", TR 94.5, U.
Sydney,, 1994.
* Joel Kelso. "A Visual representation for functional programs", TR
CS95-01, CS Dept, Murdoch Univ, 1995.
You can also have a look at Reekie's subsequent work on dataflow signal
procesing (including his phd thesis)
@phdthesis{ reekie95realtime,
author = "H. J. Reekie",
title = "{Realtime Signal Processing: Dataflow, Visual and
Functional Programming}",
address = "University of Technology at Sydney, Australia",
year = "1995",
url = "citeseer.nj.nec.com/article/reekie95realtime.html" }
or on the work
* of Launchburry on Hawk (www.cse.ori.edu/PacSoft/projects/Hawk)
* at Chalmers on Lava (http://www.math.chalmers.se/~koen/Lava),
* O'Donnell on Hydra (http://www.dcs.gla.ac.uk/~jtod/Hydra/)
The laters all use FP to describe hardware systems.
Finally, you could also have a look at
* Camlflow
(http://wwwlasmea.univ-bpclermont.fr/Personnel/Jocelyn.Serot/
camlflow.html)
a system i developed to describe data-flow graphs as caml programs.
HTH,
Jocelyn
--
E-mail: Jocelyn.Serot@l_a_s_m_e_a.u_n_i_v-bpclermont.fr
S-mail: LASMEA - UMR 6602 CNRS, Universite Blaise Pascal, 63177 Aubiere
cedex
Tel: +33.(0)4.73.40.73.30 - Fax: +33.(0)4.73.40.72.62
http://wwwlasmea.univ-bpclermont.fr/Personnel/Jocelyn.Serot/Welcome.html
Valid e-mail: remove underscores (sorry, this is prevention against
junk mail)
-------------------
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
prev parent reply other threads:[~2003-02-21 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 16:40 Oliver Bandel
2003-02-20 20:12 ` Ken Rose
2003-02-21 9:04 ` Jocelyn Sérot [this message]
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=8726DA8D-457B-11D7-8129-0003934491C2@lasmea.univ-bpclermont.fr \
--to=jserot@lasmea.univ-bpclermont.fr \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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).