Open kal247 opened 7 months ago
Yes, let's start with a new PR. Your plan looks really good.
To answer some questions:
caller
stuff in separate PRs. We can do that now and things should keep working. We don't need to wait to apply those.Hello Brian, I've open pull request https://github.com/briandfoy/PerlPowerTools/pull/570 with points 1-9, 11 from my initial post.
Hello Brian,
I'm catching up with this topic after a very long break.
There are a few changes from 2022 for which I've never submitted a PR. It's a massive simplification plus improvements and bugfixes, and it would make
perlpowertools.exe
feature complete (I think).List of changes :
bin\perlpowertools
is standalone (not generated), with dynamic tools list.-V
,bin\perlpowertools
will display the version of PerlPowerTools module itself.packer\packer.pl
has been moved and renamed asutil\packer
.perlpowertools.exe perldoc perldoc
.t/perlpowertools/
(I'm not sure it's the right place).README_PerlPowerTools.exe.pod
.List of changes to other tools in
bin
:run() if !caller() || caller(0) eq 'PAR' || caller(1) eq 'PAR'
. I've already patched the following tools :date
,echo
,factor
,glob
,units
.Future work :
packer
(but usage ok).bin
might need review/patch. See notes inpacker
header.Should I raise one (or more) PR for this?
Thank you and best regards.