On Wed, Aug 7, 2013 at 12:25 PM, Paul L. Snyder <p...@pataprogramming.com>wrote:

> If paredit is a hard sell (it was for me, the first three or four times
>  that I tried it), realizing that you can break the "balance" when needed
> by
> judicious use of kill and yank may be helpful during the transition to a
> structural editing mindset.


Structural editing, like paredit, is really the only sane way to do Clojure
code.  I honestly thing anyone who manually balances parenthesis or edits
Clojure functions in a way that doesn't preserve the structural integrity
of your expressions is just doing it wrong.  (not just doing it poorly -
but doing it wrong)

So, of course, my advice to the original poster is to just jump in and
learn paredit.  It will probably seem awkward at first, but if you invest
the effort (and it honestly doesn't take that much) to learn a better way
to edit expressions, you'll be so much better off.

In fact, I've sold several people on Clojure just by showing them how
paredit makes it significantly easier to lisp-style expressions than to
edit C-style languages with their irregular syntax.  I would jumped on lisp
years ago if I had realized how easy it was to edit instead of remembering
those painful university lisp assignments where I spent all my time
balancing parenthesis and being afraid to make simple structural changes
for fear of getting my code all messed up.

-- 
-- 
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/groups/opt_out.


Reply via email to