Oops didn't finish my thought before sending. Anyways, the point is that Clojure encourages the programmer to design functionality around functions not data structures. Because Clojure is a Lisp, this syntax can be very expressive. On Fri, Apr 24, 2009 at 12:49 PM, David Nolen <dnolen.li...@gmail.com>wrote:
> On Fri, Apr 24, 2009 at 12:15 PM, Mark Engelberg <mark.engelb...@gmail.com > > wrote: > >> >> The problem, of course, is that there is a language design principle >> that has evolved in the OO community that client code shouldn't need >> to know whether you are accessing a field or a method. In Clojure, >> things kind of break down when you switch from using something in a >> "field-like" way to a "method-like" way. >> > > One thought is that of all the Clojure libraries that out there, how many > of them are actually providing data structures that are meant to be objects? > Hardly any. > > Take for example, this example from clojureql > > (run-and-show > (sql/having (sql/group-by (sql/query [StoreName (sum Sales)] > StoreInformation) > StoreName) > (> (sum Sales) 1200))) > > > > --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
