John Goodsen wrote:
I definitely prefer the range solution over the others.
I agree, it makes sense and is simple IMO.
On Wed, Apr 22, 2009 at 2:14 AM, aslak hellesoy
<aslak.helle...@gmail.com <mailto:aslak.helle...@gmail.com>> wrote:
This is actually one of the best I've seen so far. However it
doesn't scale for multiple columns. (Imagine if you have 5 of them
- they easily get mixed up, or you make a spelling mistake).
I have also taken the meat+hamburge example and tweaked a little
bit: http://gist.github.com/99620
As you can see I'm a little sceptical of complex tables. Instead I
have invented the Range for feature writers. You specify a range
of columns you want for a column hash. (This could work along with
my example where you don't specify a range, just any token, and
get the "rest").
--
John Goodsen RADSoft / Better Software Faster
jgood...@radsoft.com <mailto:jgood...@radsoft.com>
Lean/Agile/XP/Scrum Coaching and Training
http://www.radsoft.com Ruby on Rails and Java Solutions
------------------------------------------------------------------------
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
