Hi there fellow Monks!

In the latest Perl Weekly: Issue #628 - 2023-08-07 - Have you tried Perl v5.38?

There are links to a multi-part Roguelike in Perl tutorial which is really cool (probably a first one for Perl!).
I thought it would be nice to have all these links in one convenient place to reference later, so here they are:

https://chris.prather.org/perl-roguelike-part-0.html
https://chris.prather.org/perl-roguelike-part-1.html
https://chris.prather.org/perl-roguelike-part-2.html
https://chris.prather.org/perl-roguelike-part-3.html
https://chris.prather.org/perl-roguelike-part-4.html
https://chris.prather.org/perl-roguelike-part-5.html
https://chris.prather.org/perl-roguelike-part-6.html

Enjoy! and onwards to Perl 7 !!!

I have released version 1.40 of berrybrew. It comes with some extensive changes over this, and the previous 1.39 version. (See the changes list).

User facing changes include:

• Ability to install and use the new 5.36 and 5.38 releases of Strawberry Perl
• berrybrew archives hidden command. It displays the list of portable Strawberry Perl zip files previously downloaded
• berrybrew download hidden command. Download, but do not extract the zip archive of a perl version
• berrybrew snapshot command. Export an installed perl version to a zip archive, and import a previous zip snapshot to a new installed instance

berrybrew snapshot usage:

• bb snapshot export <perl version> [snapshot name]
• bb snapshot import <snapshot name> [new instance name]

As far as changes on the developer side, the changes are significant. Here's a high-level list:

• Broke out like functionality in the main berrybrew.cs source file, and spread it across several new classes, each in their own source file
• Removed the deprecated berrybrew upgrade command. Upgrades shall be done via the installer
• Created a very extensive MANIFEST checking system for the installer. This ensures that all files that need to be installed are, those same files are removed upon uninstall, and no rogue files when building the installer are accidentally leaked in
• Added a significant amount of documentation for the development, build, test and release lifecycle of the project. If I get hit by a bus, I've created a fantastic roadmap for someone to carry on the project quite readily (bb dev docs)
• A few minor bug fixes, and one major one

-stevieb

Why Social Media Algorithms Are Failing You - Rob Malda, Slashdot Founder, Interview (youtube)

(Sorry, not steaming fresh, about 6 months old)

In case you're wondering: if vroom is our Olympian, then CmdrTaco is our Titan.

Update: The most recent release of berrybrew now includes the 5.36 and 5.38 version information, so no change of options are required to use them. As always, you can if you like review the Changes log to see what else has changed.

I forked the Strawberry Perl repo and updated the releases.json file, which berrybrew uses to know what perls are available.

One small gotcha... normally it gets this file from Strawberry Perl website, but nobody currently has access to manage it. I've created a PR to get the releases.json updated, but until the PR is merged, we can use my forked version (I will update this thread with what will become the official URL after the PR is merged. After the Strawberry site is back to being actively maintained, the temporary link can be removed, but will going forward remain valid).

To use the new perls, we have to update a berrybrew option that specifies where we get our version information:

berrybrew options download_url https://raw.githubusercontent.com/stevi
+eb9/strawberryperl.com/gh-pages/releases.json
[download]

Then fetch the new versions:

berrybrew fetch
[download]

Now they're available:

berrybrew available
[download]

Here's the entire operation:

> berrybrew options download_url https://raw.githubusercontent.com/ste
+vieb9/strawberryperl.com/gh-pages/releases.json

        download_url:    https://raw.githubusercontent.com/stevieb9/st
+rawberryperl.com/gh-pages/releases.json

> berrybrew  fetch

Attempting to fetch the updated Perls list...
Successfully updated the available Perls list...

> berrybrew available

The following Strawberry Perls are available:

        5.38.0_64
        5.38.0_64_PDL
        5.36.1_64
        5.36.1_64_PDL
        5.32.1_64
        5.32.1_64_PDL
        5.32.1_32
    …

> berrybrew install 5.38.0

Downloading https://github.com/StrawberryPerl/Perl-Dist-Strawberry/rel
+eases/download/SP_5380_5361/strawberry-perl-5.38.0.1-64bit-portable.z
+ip to C:\berrybrew\temp\strawberry-perl-5.38.0.1-64bit-portable.zip

Confirming checksum ...
Checksum OK

Extracting C:\berrybrew\temp\strawberry-perl-5.38.0.1-64bit-portable.z
+ip

The following Strawberry Perls are available:

        5.38.0_64       [installed]
    …

berrybrew switch 5.38.0

Switched to Perl version 5.38.0_64...

> exit

> perl -v (new CLI window)

This is perl 5, version 38, subversion 0 (v5.38.0) built for MSWin32-x
+64-multi-thread
[download]

Videos for The Perl & Raku Conference 2023 in Toronto have begun to appear on YouTube.

rjbs has released 5.38:

Take my advice and live for a long, long time. Because the maddest thing a man can do in this life is to let himself die.

— Miguel de Cervantes, Don Quixote

We are happy to announce version 38.0, the first stable release of version 38 of Perl 5. In other words: v5.38.0 has been released, and this is good!

You will soon be able to download Perl 5.38.0 from the CPAN at:

https://metacpan.org/release/RJBS/perl-5.38.0/

SHA256 digests for this release are:

5c4dea06509959fedcccaada8d129518487399b7  perl-5.38.0.tar.gz
2e7b1c56c1f795e8173c83a52e91218ba05ee72c  perl-5.38.0.tar.xz
[download]

The full announcement is at https://www.nntp.perl.org/group/perl.perl5.porters/2023/07/msg266602.html.

BooK writes on perl5-porters:

Just a PSA that the perldoc.pl domain has not been renewed and its registrant is sadly still out of contact. I have an option on the domain which will allow me to take ownership in a month, but until then (or the domain is renewed) it will not function. Robert has updated perldoc.perl.org to bypass the domain, so please update your links if you are still using perldoc.pl.

-Dan

Howdy! We have a full three day conference planned in Toronto, running July 11-13 -- that's just 4 1/2 weeks away!

If you haven't registered and grabbed a room yet, this is a reminder that our room block will disappear on Monday, June 19, so be sure to grab the room you want before that date.

In addition to the conference, there's going to be a hackathon on Monday, July 10, and Dave Rolsky will be putting on a one-day Go class on Friday July 14. That's all taking place at the venue, the Doubletree Hilton on Chestnut, in downtown Toronto. Please visit the conference website for more information, and I hope to see LOTS of you there!

"The only languages younger than 10 years in the current top 100 are: Swift (#14), Rust (#17), Crystal (#48), Solidity (#59), Pony (#71), Raku (#72), Zig (#88) and Hack (#92). None of them are less than 5 years old. In other words, it is almost impossible to hit the charts as a newbie. On the contrary, we see that golden oldies revive. Take for instance Fortran, which is back in the top 20 thanks to the growing demand for numerical computational power. So, if you have just invented a brand new language, please have some patience!" -- Paul Jansen CEO TIOBE Software

Crossposted from https://www.reddit.com/r/perl/comments/1344vs5/pdl_2083_released_and_updates_from_a_year_of/

A new release of PDL is out!

A summary of changes over the last year since PDL 2.077:

• PDL::IO::STL: read and write STL (stereolithography format) files that are used in applications such as 3D printing.
• Improvements to the C API and PP code generator (many in order to support writing bindings to external non-PDL code).
• Incorporation of several of Bryan Jurish's PDL::VectorValued functions into the core PDL distribution. Thank you Bryan Jurish!
• Continuing improvements to add complex number support to more PDL functions such as conv2d() and interpolate(). Thank you W. Luis Mochán & Eric Wheeler!
• Improvements to handling of badvals, NaNs, and empty ndarrays for various functions (Ufunc, setops, whereND, append). Thanks to Kieron Taylor & James Cook!
• Improvements to documentation generation for non-core PDL modules.
• New sound demo by Harald Jörg!

And finally thanks to all the folks reporting bugs!

But that's not all! There have been several exciting releases in the broader World of PDL:

• Eric Wheeler has released two modules
  • PDL::IO::Touchstone: read and write Touchstone files which are used to deal with complex-valued RF sample data.
  • PDL::Opt::Simplex::Simple: simple interface to simplex optimization.
• Vikas N. Kumar's and kmx's PDL::Finance::TA has seen many improvements. You can use it through a Prima-based GUI at App::financeta.
• Ingo Schmid and Ed (@mohawk2) have released a PDL interface for OpenCV at PDL::OpenCV. Many of the updates to the code generation in the past year have been motivated by this release!
• (self-plug) AI::TensorFlow::Libtensorflow: bindings to the low-level libtensorflow deep learning library. Several demos are available in the release and usable via Docker.
• David Mertens has graciously given co-maint out for PDL::Drawing::Prima and PDL::Graphics::Prima. With many fixes to bring the code up to date with the latest Prima thanks to Dmitry Karasik, this now works again for use as a plotting engine for PDL::Graphics::Simple. There are also some updates to David's https://github.com/PDLPorters/App-Prima-REPL to bring it up to date.
• Dmitry Karasik has also released updates to PDL::PrimaImage.
• Several updates to PDL::Graphics::Gnuplot including use of Alien::Gnuplot to install a working Gnuplot.

• fix some memory leaking - thanks Yury Pakhomov for report
• fix various problems with empty ndarrays - thanks @falsifian for report/tests
• no more HTML doc generation
• PDL::Doc::add_module now adds all submodules of given namespace (#420)
• OtherPars can now be incomplete arrays of pdl* (#421)
• add sound demo - thanks @HaraldJoerg
• inplace operations no longer copy input arg if inplace

The IRC channel (#pdl on irc.perl.org) is a great virtual place to come and ask questions, or just watch the GitHub messages flow by.

Please give the new release a try and report problems.

The Strawberry Perl project has put out a developer pre-release of Strawberry Perl. There are some modules missing still (DBD::Oracle, PDL, Crypt::OpenSSL::DSA for example), but if you use Strawberry Perl, please test it and provide feedback via Github.

If you can help with the open tickets, your help getting the modules included in Strawbery Perl is certainly appreciated.

• fix build issue with "invalid register for .seh_savexmm"
• add ppport.h
• add core_bools and encode_core_bools methods to support builtin::true and false on perl >= 5.36

  core_bools also works towards compatibility with JSON::PP, and with both of these options it is possible to have correct, full round-trip encode/decode between Perl and JSON booleans.

• fix floating point precision issues with -Duselongdouble and -Dusequadmath
• fix intermittent garbage in floating point numbers from encode with -Dusequadmath (fix taken from Cpanel::JSON::XS ad072b4)
• drop common::sense as a direct dependency (it's still used indirectly via Types::Serialiser, though)
• fix repository and issue tracker for CPAN (thanks to Gabor Szabo)

Those who previously reported build failures, could you please retest?

I'd also be interested in benchmarks on various configurations. The distribution now includes a bench_simdjson.pl in the eg directory, just run it with as many JSON files as you'd like. If you report benchmark results, please include the CPU type and the output of JSON::SIMD::simdjson_version as well.

With this version, I think I've added everything I've wanted. In the future I'll intend to track new releases from both JSON::XS and simdjson, and of course I'd fix any reported bugs ASAP. (There is one major new feature I'm thinking about, the ability to have partial/deferred decodes and precomputed encodes similar to Go's json.RawMessage, but I don't have a clean and safe design for it yet, so it'll have to wait. I don't want to add ad-hoc features haphazardly.)

I hereby announce the release of a new JSON encoder/decoder module called JSON::SIMD.

It is a fork of JSON::XS where the decoder was replaced with simdjson, a recent high-performance C++ JSON parser that uses SIMD instructions found in newer CPUs to make decoding as fast as possible.

The module is intended to be a drop-in replacement for JSON::XS, indeed the encoder part is unmodified, and the legacy decoder is kept to support the functionality that could not be implemented with the simdjson decoder. But for the most common scenarios the simdjson decoder is the default, offering a speedup ranging from a few percents to 100+%, depending on the size and structure of the JSON document and the available instruction set. See the documentation for benchmarks.

The interface is mostly the same as that of JSON::XS, with one notable addition: there is a new method decode_at_pointer, which leverages simdjson's ability to quickly scan through the document to return just a part of the document, without needing to decode and allocate for the rest.

Example:

my $large_json = '{
   "ignore": "this",
   "don't need": ["these", "either"],
   "foo": ["bar", {"baz": "quux"}]
}';
JSON::SIMD->new->use_simdjson->decode_at_pointer($large_json, '/foo/1'
+);
=> {bar => 'quux'}
[download]

I'd be interested in seeing benchmarks - if you create one, please include the output of simdjson_version as well.

FAQ (Facetiously Anticipated Questions):

Why a new module?

When I came across simdjson, I've looked at the section in their documentation that listed the available ports and bindings, and noticed that one particular language was conspicuously missing. I wanted to remedy that situation.

Why JSON::XS?

I didn't want to start with a clean slate, because I saw value in having the encoder and decoder in the same all-in-one package, and I didn't want to rewrite the encoder part from scratch, so it was logical to start from an established module. JSON::XS was chosen as the basis for the fork because I has been using that module at $work and elsewhere without problems, so preserving compatibility with it was seen as an important goal.