Closed ahmogit closed 1 month ago
Duplicate of https://github.com/makamaka/JSON-PP/issues/88.
OK, sorry for the noise.
Before filing this report, I did search for "json_pp" in both open and closed issues in the perl/perl5 repo, but didn't see it listed. What was the right way to have searched for it in order to find that it had already been reported?
The way I did it: I first looked where in the repo the json_pp
file is located. I found it in cpan/JSON-PP/bin
, which tells me it is maintained on CPAN in the JSON-PP distribution (everything under cpan/
is maintained elsewhere and only imported into perl). JSON::PP is on metacpan as https://metacpan.org/pod/JSON::PP and has an "Issues" link (left sidebar) that leads to https://github.com/makamaka/JSON-PP/issues. There are only 7 open issues, so it was easy to find the report about "duplicate specification".
OK, thanks for that info.
The reasoning that led me to file the issue on the perl/perl5 tracker was simply that the json_pp executable is provided in the perl-5.40.0 distro package. I did not realize that perl5 pulled it, in turn, from cpan, so thanks for educating me on that.
Description Running json_pp with no args issues (harmless) diagnostic from Getopt::Long:
Looks like it may be missing the "no_ignore_case" configuration option, i.e.
Getopt::Long::Configure('no_ignore_case');
Steps to Reproduce $ json_pp
Expected behavior No diagnostic should issue, it should just wait for stdin.
Perl configuration
See attached output from perl -V.
perl-V.txt