Reginald Meeson wrote: > Mads -- > > Eons ago, colleagues and I put together a primitive data flow diagram > editor and generated functional code for the functions users wired > together. One of the things we learned was that people would happily > wire together diagrams with state components that could not be > translated because they did not represent functions. (Two different > data flow paths sharing the same state creates obvious race conditions, > but that's what some people wanted to draw.) > > It was an interesting exercise to build the tool, but I don't think > it gave users any great advantage. Perhaps is was a shortcoming of > the tool, which was little more than a prototype. However, the > informal nature of data flow diagramming at that time seemed to be > out of synch with the rigor needed for programming. Good luck with > your search -- it may be a good time to try it again.
Do you have any papers or other kind of documentation describing the system? what worked and what did not work? -- Mads Lindstr�m <[EMAIL PROTECTED]> _______________________________________________ Haskell mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell
