I am not sure, if there are any scholarly articles about structured programming style guidelines for visual programming languages. I've seen only rules-of-thumb. hey, there is not even a "return" command (to a main program?). only inlets and outlets. I am not even sure about the analogy of function, class, object when comparing C or C++ to a graphical dataflow programming language (which pd is?). actually, the data is not flowing at all, it is the objects' function code that pilgers to the sanctuaries of stored data and accomplishes its task there... marius.
Dudley Brooks wrote:
Can anyone direct me to articles on constructing clear, modular, non-spaghetti patches in pd or other visual dataflow languages? Especially if the articles derive their recommendations from theoretical analysis (as with the investigations that led to structured programming in imperative languages), rather than just rules-of-thumb -- although the latter are useful also.
Or is some amount of spaghetti unavoidable in dataflow languages, perhaps because it is inherent in the situation being modeled, rather than being an artifact of the language?
Thanks.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list