An alternate design is to derive from Foo::Parse.
This is the way I normally do it - but I do use callbacks sometimes, and the code you have above seems fine to me, albeit quite simplified. Note that $self in the callback doesn't make much sense - it's a Foo::Parse object, and the callback is not a method of Foo::Parse. Better to name it $obj or $fp. In fact, if you split it a bit, you don't need to pass back the object at all:package Foo::Parse; #... sub parse { my $self = shift; if (my $func = $self->can('action')) { $self->$func(@_); } } #... package Foo::Parse::Splitter use base 'Foo::Parse'; sub action { my $self = shift; # ... } package main; my $fp = Foo::Parse::Splitter->new('FooParser'); $fp->parse($_) while <>;
This makes it into a closure, meaning that $fp remains visible. Even if $fp were itself no longer in scope, this closure can still see it. This is even more normal to me.my $fp; $fp = Foo::Parse->new('FooParser', sub { local $_ = shift; s/^\w+:// or $fp->warn("something wrong!"); split /,/; } );
In reply to Re: Seeking advice for OO-related strategy
by Tanktalus
in thread Seeking advice for OO-related strategy
by blazar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |