On Thursday, 8 October 2015 14:21:13 UTC+1, Jason Stewart wrote: > > Designing a FP program often involves looking at the data first, then > thinking about what transformations that the data needs in order to become > what you want it to be. I like to think of functions as instructions about > how to transform that data. > > This is overly simplistic, and I would definitely recommend some > background reading/watching of videos. > > Thanks, Jason. This is the sort of hint I was hoping for. :) [*Aside: I'm the sort of Luddite that doesn't like to watch videos on a computer; that's what TVs are for. Yes, I know. Be kind. We all have our failings. ;)*] I shall be seeking out the Brian Marick book ASAP. If anyone has any more such high (abstract) level comments like this, I'd love to read them...?
So, am I right, at this highly-simplified level, that a functional program will tend to look (to an OO programmer) like a simple series of function calls or maybe a Unix shell script? Of course the 'functions' (or shell script calls) are native/library functions of the FP language, but is that roughly right? -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
