> I think if you're writing in a functional style the repl is more of a > win. The things you're writing/testing tend to be smaller, more self- > contained, not as much stateful setup.
I agree. My post-python life has been filled with this sort of experimentation. I find myself frequently writing small functions and wanting to simply prod at them. Firing up Eclipse or Netbeans sometimes feels to heavy. I find that if I'm able to experiment with what I'm building in the REPL, it's usually sort of a gauge of other properties I'm after -- testability, for example. On Thu, Jun 16, 2011 at 7:32 AM, Steve Lindsay <[email protected]> wrote: > On Jun 16, 12:58 pm, Cédric Beust ♔ <[email protected]> wrote: >> >> Again, a REPL is very limited for >> this and only useful for very trivial situations. >> > > I think if you're writing in a functional style the repl is more of a > win. The things you're writing/testing tend to be smaller, more self- > contained, not as much stateful setup. Change a function, evaluate in > the repl, test it with a few different inputs, make some more changes, > re-evaluate, re-test etc. It's not so much that you're presented with > a situation and you think "this calls for a repl!", it's that your > general workflow is different. Not trivial at all. > > - Steve > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- Jeb Beich http://www.jebbeich.com -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
