comment on

I suppose I could also use this :-)

my $s = Scope->new( probe => $netlist )
             ->anatrace(
                 in    => [ 'System input', 'active', 1 ],
                 out_1 => [ 'Lpf bank1', 'active', 1 ],
                 out_2 => [ 'Lpf bank2', 'active', 1024 ],
                 out   => [ 'System output', 'active', 1 ],
                 bank2 => [ 'Switch pos', 'active', 1 ],
               )
             ->generate();
[download]

The => after the first arguments look nice, especially since the first arguments are instance handles, and I use them as a hash key.

In this example the arguments to anatrace really aren't mutators, they are constructors of sub-objects. They are waveforms being added to a scope display.

update
Is the problem that you perceive just with mutators, or does it also apply to sub-object constructors? Can you provide examples of acceptable method chaining, and contrast it with problematic method chaining?

It should work perfectly the first time! - toma

In reply to Re^3: Mutator chaining considered harmful by toma
in thread Mutator chaining considered harmful by Aristotle

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.


XP is just a number
	PerlMonks