Re:Reasons To Give The Vim Text Editor A Chance
by jrockway on Monday May 16, 2011 @12:36AM
(#2551658)
Someday, you'll want to run your code more than once, and you'll write tests instead of typing them into the REPL.
[ Parent
| on HN ]
Re:Reasons To Give The Vim Text Editor A Chance
by eropple on Monday May 16, 2011 @10:06AM
(#2552528)
Print statements aren't meaningful tests, though. Hence the eight hojillion xUnit ports for pretty much every major language.
Re:Reasons To Give The Vim Text Editor A Chance
by jrockway on Tuesday May 17, 2011 @02:04AM
(#2555472)
OK, so say you have some test that creates a foobar object and invokes the method baz, which does some stuff that you care about. The test fails. What do you do? Do you pick apart the implementation of baz in the REPL, or do you add some print statements inside baz?
The second option is easier. You obviously remove them once your understanding (and tweaking) of the code leads to a passing test.
Re:Reasons To Give The Vim Text Editor A Chance
by japherwocky on Tuesday May 17, 2011 @01:00PM
(#2556966)
you set a trace point inside baz, investigate with the REPL, and fix your code.
Re:Reasons To Give The Vim Text Editor A Chance
by japherwocky on Monday May 16, 2011 @04:19PM
(#2553997)
wait.. what? are you scanning stdout with your tests?