Many thanks for the thoughtful replies to my question. Successively, they pointed out that
- I was, as so often, missing the obvious by not sub-classing
- but that the creation of a new class implies, to me at least, a more stable setup than I wanted;
- but then that there's quite an easy way to change a class-wide method definition, which was good enough for me
- and that finally, there's a way of doing it the original way I had conceived anyway.
In the end, subclassing was easiest, and mostly fitted what I wanted to do. After all, it's a test script, which for me only needs to test elegant code, not be elegant code itself.
As an aside, the reason that I'd originally thought of approaching it by runtime method redefinition is probably a habit from Ruby (please don't curse me for mentioning it in this holy place). Ruby has a cute of way of doing this (and so, maybe will Perl6?):
class Dog
def bark
puts "woof"
end
end
fido = Dog.new()
rover = Dog.new()
class << rover
def bark
puts "meow"
end
end
fido.bark() # woof!
rover.bark() # meow!
Once again, thanks for your replies
-
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.
|