With people occasionally talking about "Code vs.
Data", it only makes sense that you should be able process over code as you would a string. Sexp Path is a code processing tool that allows you to search over and process Ruby code in the form of S-Expressions.
Version 1.3.2 not only has a bunch of bug fixes (including supporting https URLs for gem sources) and improvements, but a number of
We've all heard the admonitions: "Don't Repeat Yourself!" But how do you avoid this if you're working on a Ruby codebase that stretches to thousands of lines, maintained by multiple developers?