sub x
{
print "Starting with X\n";
my $ret = _shared_code(@_);
return "From X: $ret";
}
sub y
{
print "Starting with Y\n";
my $ret = _shared_code(@_);
return "From Y: $ret";
}
sub _shared_code
{
# Do stuff here
}
You still get the shared code abstracted out and you get to handle differences. I often do this with structures like:
sub DoFoo { return do_stuff('Foo', @_) }
sub DoBar { return do_stuff('Bar', @_) }
sub DoBaz { return do_stuff('Baz', @_) }
sub do_stuff
{
my ($name, ...) = @_;
# Do stuff here
}
This is usually one of the first steps I take when refactoring a bloated code base.
------ We are the carpenters and bricklayers of the Information Age. Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement. Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|