There's no way to define a sub to have the same syntax as print

I always thought function $foo $bar is another notation for $foo->function($bar) (which is also often used to imitate the new operator from other languages). So for example the following works: 

use warnings;
use strict;

my $mp = MyPrint->new(*STDERR);

$mp->myprint("foobar\n");
myprint $mp "foobar\n";

package MyPrint;

sub new {
    my ($class, $out) = @_;
    return bless { out => $out }, $class;
}

sub myprint {
    my ($self, $text) = @_;
    my $out = $self->{out};
    print $out $text;
}

[download]

I don't really know why STDERR->print "foobar" doesn't work though. It dies with 

Can't locate object method "print" via package "IO::Handle"

[download]
although the documentation says something else.

In reply to Re^2: prototypes for dual-file handle print? by Anonymous Monk
in thread prototypes for dual-file handle print? by iaw4

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.