in reply to Re^2: Blessing with unknown classnames
in thread Blessing with unknown classnames

"Minor issue: finding the classname (e.g. ref($ret)) is part of deciding if sub returned an error, for example when sub normally returns a blessed object instead of unblessed ref (as in my example)."

Sorry, but I don't understand this. My code using blessed clearly distinguished "Error" from "Success". Your line: 

die "@$ret" if ref($ret) eq 'YouveGotError';

[download]

could be rewritten as: 

die "@$ret" if $err eq 'YouveGotError';

[download]

If I change 'blessed $ret' in my code, to 'ref $ret', the output becomes: 

Run: 1
Error "ARRAY" detected
Code: 42
Errstr: 43
Run: 2
Error "YouveGotError" detected
Code: 0
Errstr: error was ...

[download]

which, I'm pretty sure, is not what you want.

I suspect we may be talking at cross-purposes, or there's some other misunderstanding; however, I've looked back over our posts, and can't see what the problem might be.

"apropos the edits: ..."

No need to apologise. I just wanted to make it clear what I was responding to. There was no intended rebuke or other negativity.

— Ken

Replies are listed 'Best First'.
Re^4: Blessing with unknown classnames
by bliako (Abbot) on Apr 01, 2021 at 19:42 UTC

    I mean this: if (defined $err) can become if (defined($err) && ($err eq 'YouveGotError')), so that it errors only on'YouveGotError' blessed refs and nothing else, because the sub may normally return other blessed things.

[reply]
[d/l]
[select]
      I mean this: if (defined $err) can become if (defined($err) && ($err eq 'YouveGotError')), so that it errors only on'YouveGotError' blessed refs and nothing else, because the sub may normally return other blessed things.

      I'm not sure if this is a question, but just in case, note that I fully agree with kcott that Scalar::Util's blessed (a core module) is the "correct" answer to the question of how to tell if a reference is blessed or not. But if the sub also can return other blessed refs, and you want to differentiate them, then one possible solution is what you said in your root node: creating an "error" class is one way. But since Perl's OO system is so nice and simple, inheritance can be incredibly simple, as I show in the following example. Of course, there are existing solutions on CPAN, e.g. Throwable and Exception::Class.

      use warnings;
use strict;
use Scalar::Util qw/blessed/;

@Error::ISA = qw//; # "base class" for errors
@BadInput::ISA = qw/Error/;
sub doit {
    my $in = shift;
    if ( $in =~ /foo/ ) {
        return bless [123,456], 'RealReturnValue';
    }
    else {
        return bless ['abc','def'], 'BadInput';
    }
}

for my $val ("foobar", "quzbaz") {
    my $ret = doit($val);
    if ( my $err = blessed $ret and $ret->isa('Error') ) {
        print "$val -> Error: $err\n";
    }
    else {
        print "$val -> OK\n";
    }
}

__END__

foobar -> OK
quzbaz -> Error: BadInput

      [download]
[reply]
[d/l]
[select]
        @Error::ISA = qw//; # "base class" for errors
@BadInput::ISA = qw/Error/;

        [download]

        Neat! I guess this is some kind of "class autovivification" you are doing?

        e.g. Throwable

        I prefer to keep it simple and mooless

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom