On Apr 5, 2010, at 7:49 AM, Sophie wrote: > Is this a Clojure restriction, or is it intrinsic to functional > programming?
It's a consequence of immutable data structures, which are an aspect of functional programming. An immutable object can never be changed, and you can't create multiple objects simultaneously, so you can't ever get a cycle of direct references between immutable objects. > If my app is essentially about a user creating and editing a graph > structure (sometimes via crud-level interactions, other times by > somewhat larger refactorings), is either Clojure or functional not a > good match? You can still do things functionally, with a level of indirection. I don't see any problem with that approach, but whether it's a good match for your project is up to you. Otherwise, you can use mutable structures. Clojure certainly supports mutability, but as a primarily-functional language it might not be the right tool for the job if you're going to use mutability extensively. -Michael -- 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 To unsubscribe, reply using "remove me" as the subject.
