Yes, over fifty words longer. Mnemonics won't be much help...which is why Raku provides better options. Regarding the hash suggestions, is this what programmers usually do? . . . put all variables in a hash and bounce them around to the various subroutines, even if a given subroutine might use but a few of those variables? To my mind, that's not the purpose of a hash, and it's why I've tried, instead, to make them all global variables--because so many subroutines depend on a particular subset of them. But Perl 5 has no good options for that...I've become disgusted with the best options suggested (including putting all of my globals in a separate package file--it's a very cludgy "solution" which doesn't work well). Apparently, I'm the only one who ever needs scores of variables passed into a single subroutine...and I'm the only one who tries to organize my 30,000+ lines of code into separate files that should all be part of the "main" package. I've learned that "strict," for example, will not work properly when spanning multiple files. I've been tempted to create a script that dumps all my files together into a single file after I've finished editing them in their separate (organized) spaces--just to make Perl happy and run well. Raku appears much better organized, and I'm really hoping it will be the solution I've been needing. From everything I've read, it looks like it will be the answer.
Blessings,
~Polyglot~
In reply to Re: Ordering of parameters - Re^9: Converting Unicode
by Polyglot
in thread Converting Unicode
by BernieC
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |