If you don't run into graphs you are either solving very peculiar problems, or you don't recognize them when you see them. They are everywhere.<br><br><div><span class="gmail_quote">On 6/22/07, <b class="gmail_sendername">
Andrew Coppin</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dan Piponi wrote:<br>> Andrew said:<br>><br>>> True enough - but that's a rather specific task. I'm still not seeing<br>>> vast numbers of other uses for this...<br>><br>> Graphs are one of the most ubiquitous structures in the whole of
<br>> computer science. Whether you're representing dataflows, or decoding<br>> error-correcting codes, or decomposing an almost block matrix into<br>> independent parts for multiprocessing, or figuring out which registers
<br>> to spill in a compiler, or programming neural networks, or finding the<br>> shortest path between two cities, or trying to find dependencies in a<br>> sequence of tasks, or constructing experimental designs, or using an
<br>> expert system to diagnose disease symptoms, or trying to find optimal<br>> arrangements of marriage partners, or a million other tasks, graphs<br>> appear everywhere!<br><br>I see *trees* around the place a lot, but not general graphs.
<br><br>Maybe it's just the type of problems I attempt to solve?<br><br>_______________________________________________<br>Haskell-Cafe mailing list<br><a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org