Punching bag? Bro, be honest. People have only tried to help you here and every single time, you've shot down their wise advice. Over and over, you mention a problem you're having, provide a peculiar reason why you won't implement their solution, and then wrap things up by blaming Perl for allowing you to write garbage code without immediately blowing up.

But I cannot imagine the mess I'd be in by trying to create a unique hash for every subroutine just to accommodate its particular requirements for incoming variables. I think I'd rather have a single hash with all of them than to have the nightmare of so many hashes that were hard to keep track of.
Post your code somewhere. I remember you hate the idea of putting code on github but put it somewhere because I wanna see it. We gotta see the function that uses fifty different parameters every time it's called. You keep talking about it but we (apparently) can't help without seeing the code itself.
Being unable to use references/dereferences, etc. (like what is a "hashref"...I just don't get it), Raku's named parameters is a wonderful way of keeping things concrete without layers of so-called abstraction.
Here, since you think Raku will solve all your problems where Perl cannot, here's an example of Raku's named parameters:

sub distance(:$from, :$to) { $from - $to }

say distance(from => 30, to => 10);

[download]

That's taken directly from https://course.raku.org/essentials/functions/named-parameters/. Here's one of a few ways that could be written in Perl (this example is core 5.36 or better):

use 5.36.0;
sub distance(%args) { $args{from} - $args{to} }

say distance(from => 30, to => 10);

[download]

The two snippets behave the same way. If you can understand one, surely you can understand the other. In fact, because you're using a hash reference in the perl version, you can pass along only the variables you need and not all 50. For example, you can do say distance(from => 30, to => 10, extra => 'yeah');, or say distance(from => 30);, or even say distance( ); and the logic in that function can do different things based on the incoming named parameters. See?

I'm thinking you should take a break from writing code for a while and wrap your mind around basic OOP concepts though. In Perl, Raku, or any other language. The more you write about it, the more I'm convinced that's the solution you're looking for.

In reply to Re^4: Ordering of parameters - Re^9: Converting Unicode by SankoR
in thread Converting Unicode by BernieC

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.