Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Tuesday November 18, 2003
11:30 AM

Integrate testing with your editor

[ #15844 ]

Emacs (and maybe some versions of vi) can integrate with your compiler, running the compile for you and automatically jumping to the line in your code where the compiler indicates an error.

What if your editor were integrated with your test suite? It could run the test suite for you and jump to the location in your test program where a test failed. You could then use whatever etags-like feature your editor provides to jump to the routine that failed.

Just a thought. I keep thinking I'd like to become an editor wizard but haven't done it yet.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.