Re: Style for mutable data

2010-01-30 Thread Johann Hibschman
On Jan 30, 4:35 pm, ataggart wrote: > Akin to what Johann said, why bother with the functions that deal with > the value/state? Put another way, the cell has identity over time, > thus implemented as a ref. A function that, say, prints a cell, should > take a cell/ref as its arg. This is my gener

Re: Style for mutable data

2010-01-30 Thread ataggart
Akin to what Johann said, why bother with the functions that deal with the value/state? Put another way, the cell has identity over time, thus implemented as a ref. A function that, say, prints a cell, should take a cell/ref as its arg. Probably more than you need, but I highly recommend Rich's ta

Re: Style for mutable data

2010-01-30 Thread Mark Engelberg
How about Cell? -- 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, sen

Re: Style for mutable data

2010-01-30 Thread Jeff Schwab
Johann Hibschman wrote: Does anyone have style suggestions for distinguishing the states from the refs to mutable data? Let's say I'm manipulating a cell in a lattice, or doing dynamic programming, or something. In any case, I have a cell. ;; Current convention: use "cell-" as the type of the s

Style for mutable data

2010-01-30 Thread Johann Hibschman
Does anyone have style suggestions for distinguishing the states from the refs to mutable data? Let's say I'm manipulating a cell in a lattice, or doing dynamic programming, or something. In any case, I have a cell. ;; Current convention: use "cell-" as the type of the state of a "cell". (defstru