develooper Front page | perl.perl5.porters | Postings from January 2022

Re: Things you can't do in a signatured sub

Thread Previous | Thread Next
From:
Dan Book
Date:
January 20, 2022 05:32
Subject:
Re: Things you can't do in a signatured sub
Message ID:
CABMkAVXdVTF=zKhp8-w9aooHgjO=rNF7wyq2=f=sw=ai5Hh=Ag@mail.gmail.com
On Thu, Jan 20, 2022 at 12:20 AM Darren Duncan <darren@darrenduncan.net>
wrote:

> On 2022-01-19 12:43 p.m., Alexander Hartmaier wrote:
> > I have one sad example to add: defining a sub that is passed as a
> callback to a
> > module which doesn't document the (number of) arguments and call it in
> different
> > parts with a different number of arguments. Example I'm just dealing
> with is
> > Mojo::RabbitMQ::Client.
> > In the end I gave up and didn't specify a signature to avoid exceptions
> caused
> > by the different number of arguments.
>
> So here's a question.  The way signatures work now, if one puts "@" at the
> end
> of the signature, does that say silently accept but throw away the extra
> arguments, or is there some way in a signature to say explicitly that you
> take a
> variable number of arguments and there is an array you can get "the rest"
> in?


($arg, @rest)

-Dan

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About