While this discussing has taken a slight tangent from my original question, it's been a very interesting read. Thanks for all your thoughts everyone. You guys rock!
On 18 October 2014 08:28, Mark Engelberg <mark.engelb...@gmail.com> wrote: > Yeah, it's hard to deny the convenience of Clojure's keyword lookups and > standard assoc mechanism for getting and setting stored values, but I think > Bertrand Meyer's Uniform Access Principle reflects some pretty deep > thinking about the kinds of complications that arise in maintaining large > programs. Although the Clojure community mostly rejects the Uniform Access > Principle right now, as people start writing larger programs in Clojure, > and need to maintain them for longer periods of time, it will be > interesting to see if the pendulum swings back in favor of uniform access. > > It will be fun to have this conversation again in 5 years time. > > The good news is that if the community does start to see more value in > uniform access, achieving that is just a few macros away. > > --Mark > > On Fri, Oct 17, 2014 at 10:49 PM, Mars0i <marsh...@logical.net> wrote: > >> On Thursday, October 16, 2014 11:53:42 PM UTC-5, puzzler wrote: >>> >>> In Clojure, non-computed fields are usually accessed directly by >>> keyword, whereas computed fields require an actual API. This difference in >>> access style complicates things if you want to change which things are >>> stored versus computed. >>> >> >> This also means that you have to remember which data has a keyword >> accessor and which uses a function. >> >> -- >> 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. >> > > -- > 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 a topic in the > Google Groups "Clojure" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/clojure/v03o5MWys9E/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
