You know, some days your module names just ain't gonna work. I needed to write a simple utility which would take a string of multiple SQL statements, strip out comments and also split it into individual statements. After struggling to come up with an appropriate module name, I finally started writing my tests. That's when I realized what a very, very bad choice I had made:
#!/usr/bin/perl
use strict;
use warnings;
use Test::More qw;
my $STRIPPER;
BEGIN {
$STRIPPER = 'SQL::Stripper';
use_ok $STRIPPER or die;
}
easy!
jhi on 2006-07-26T10:27:15
Just rename it to SQL::ExoticDancer.
Tidy
bart on 2006-07-26T11:12:51
The names for code reformatters appear to fall into the "tidy" or the "pretty"/"pretty printer" categories. So, how about SQL::Tidy?
I know what you mean...
sigzero on 2006-07-26T11:40:19
I also use Tcl and when I wanted to test something out quickly I would create a script called "test.tcl". My boss pointed out that one to me.
Random, inane comment
djberg96 on 2006-07-26T13:49:00
I'll bet my $STRIPPER can beat up your $STRIPPER.
It takes two to make a thing go right
hex on 2006-08-01T11:56:33
Now you just need to work out a way to use Getopt::WonderBra in there and you're all set.
