On Sat, 30 Sep 2017 12:45:09 -0700, sjn-perl...@pvv.org wrote:
> I think this bug can be closed.
Agreed. Rejecting.
I see little reason to muddy up the Usage even more with type information,
where you're mostly limited to Int/Str types anyway, and variable name
helps know which to use.
The type
On Sat, 30 Sep 2017 12:45:09 -0700, sjn-perl...@pvv.org wrote:
> I think this bug can be closed.
Agreed. Rejecting.
I see little reason to muddy up the Usage even more with type information,
where you're mostly limited to Int/Str types anyway, and variable name
helps know which to use.
The type
I think this bug can be closed.
Here's my reasoning. For me, a major point with the auto-generated usage text
is that it helps the developer of the program see the importance of picking
good variable names. If a dev chooses to name them $integer1 and $integer2
(which are obviously horrible vari
> In the original report, an argument can be made that the programmer ought to
> have made the program more useful by writing
>
>sub MAIN (Int $integer) { ... }
What if there are two integer params? MAIN (Int $integer1, Int $integer2) looks
bad and subroutine body may be hard to understand.
# New Ticket Created by Pawel Pabian
# Please include the string: [perl #125251]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=125251 >
Named params print required types:
17:33 bbkr: r: sub MAIN (Int :$x!) {...}
17:33 cameli
