Don't complicate the code, just make more methods. In OO they are cheap to add. (
Re: OO design: returning string and/or special value (peephole Object) preempted me.)
I don't like the suggestion from Re: OO design: returning string and/or special value, flags are a code smell.
use Moops;
use Data::Dx;
class Special;
class Foo {
method _actual_work { return 'foo', Special->new }
method my_method(--> Any) { return $self->_actual_work }
method my_method_special(--> InstanceOf['Special']) { return ($sel
+f->_actual_work)[1] }
method my_method_string(--> Str) { ($self->_actual_work)[0] }
}
my $f = Foo->new;
Dx $f->my_method;
Dx $f->my_method_special;
Dx $f->my_method_string;
I also experimented with
multi-methods, but unfortunately Perl is too irregular to allow dispatch on return types.
PS: Curate GET
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.