So there is no standard for it, right ? People do what they know best ? On 11 Mai, 16:04, Sean Devlin <francoisdev...@gmail.com> wrote: > Put the homoiconic nature of Clojure to work. Make a variation of > clojure.inspect and use it to create charts of program flow, or tweak > your own version of autodoc. Take full advantage of metadata. > There's a ton of long hanging fruit here if you just go looking for > it. > > My $.02 > > Sean > > On May 11, 9:45 am, Donell Jones <alliwantisca...@googlemail.com> > wrote: > > > > > > > Thanks for your reply. I think flowchart make sense but I can´t > > imagine how a big project can be visualised with that (???). > > > I think no manager in the world would make a big project without a > > good documentation ... nah I know there are some :) > > > On 11 Mai, 15:01, Jarkko Oranen <chous...@gmail.com> wrote: > > > > On May 11, 11:18 am, Donell Jones <alliwantisca...@googlemail.com> > > > wrote: > > > > > Hi Team, > > > > I am really interested in functional programming. But I am asking > > > > myself, what if the project get bigger, like the software Runa realise > > > > with Clojure. In OOP we got diagrams like UML to visualise this. But > > > > what can we do in FP ? Are there any diagrams that can be used to > > > > explain things ? > > > > > I think this is very important when it comes to documentation. > > > > I think a flowchart might be useful. In functional programming there > > > is a tendency to model things as a pipeline of transformations, > > > instead of as interactions between code modules (classes), so > > > visualizing how your data flows from its source to its endpoint will > > > be useful. > > > > On a larger scale you might want to map out the relationships between > > > namespaces, which procedures deal with state, etc. > > > > Unfortunately I don't know any tools to generate call graphs and such > > > from clojure code, but hopefully my suggestions will at least inspire > > > a few ideas. > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Clojure" group. > > > To post to this group, send email to clojure@googlegroups.com > > > Note that posts from new members are moderated - please be patient with > > > your first post. > > > To unsubscribe from this group, send email to > > > clojure+unsubscr...@googlegroups.com > > > For more options, visit this group > > > athttp://groups.google.com/group/clojure?hl=en > > > -- > > You received this message because you are subscribed to the Google > > Groups "Clojure" group. > > To post to this group, send email to clojure@googlegroups.com > > Note that posts from new members are moderated - please be patient with > > your first post. > > To unsubscribe from this group, send email to > > clojure+unsubscr...@googlegroups.com > > For more options, visit this group > > athttp://groups.google.com/group/clojure?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group > athttp://groups.google.com/group/clojure?hl=en
-- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en