<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Paul L wrote:
<blockquote
cite="mid:856033f20709241443t596d6ea0mcd6bc0f067fe9fd4@mail.gmail.com"
type="cite">
<pre wrap="">We recently wrote a paper about the leak problem. The draft is at
<a class="moz-txt-link-freetext" href="http://www.cs.yale.edu/~hl293/download/leak.pdf">http://www.cs.yale.edu/~hl293/download/leak.pdf</a>. Comments are welcome!</pre>
</blockquote>
Interesting. Now that I know the "basic Haskell" stuff these arrows
make much more sense. However, they look *very* similar to a visual
programming language and IDE my former colleagues and I developed for
doing realtime particle effects on videogame consoles. This language
contained special constructs to avoid space/time leaks, like a
dedicated "feedback loop". I hope I won't come to the conclusion that
after one year learning the cool lazy functional programming language
Haskell (which I want to use for making simple videogames in a clean
way for teaching), I got back from where I started :-) Of course that
will not be the case, I'm really learning a lot. Even if it turns out
Haskell is not really suitable for games, I will have learned a lot.
However it is very important for my goal that the code looks very
concise and clean, and having to chase hidden space/time leaks would
ruin the elegance.<br>
<br>
A minor detail in your paper: on page 7, you represent <tt><b>(d) sf1
&&& sf2 </b></tt>as a big box taking one input and
producing two outputs. The input is internally split using a Y. This
does not seem consistent with the other boxes (e.g. <tt><b>first </b></tt>or
<tt><b>loop </b></tt>internally) that show two arrows for an
incoming/outgoing pair, so I would say the outer box of &&&
would also have two inputs and two outputs.<br>
<br>
Best regards,<br>
Peter Verswyvelen<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>