113-bit integer arithmetic
Changes for 0.04
- Allow negative values to be passed to bitwise operators (&, |, ^, ~, >>, <<). These negative values will be converted to their 113-bit 2s-complement value prior to being acted upon by the bitwise operator - thus mimicking perl's treatment of negative 32-bit/64-bit IVs.
- Add divmod() function.
- Add new test file t/bitwise_feature.t
Extend Plack::Middleware::Debug with some specific panels for Dancer
Changes for 0.04
- Change ownership to Dancer Core Team
- Fix prereqs for dzil
Let Plack::Middleware::Session handle Dancer's session
Changes for 0.02 - 2024-04-13T21:40:04Z
- Show Dancer Core Team as new maintainer
Text::Xslate wrapper for Dancer
Changes for 0.04 - 2024-04-13T21:28:20-04:00
- Change docs to show maintainer is now Dancer Core Team
- Fix initial release date to make tests happy
HTTP/2 Dynamic Benchmarks (PHP vs. ModPerl2), 2024 edition.
I ram these about four years ago, and the time differentials were about the same then as now. Monolithic POSIX-threaded server architectures like mp2 + mpm_event will always dominate in low-latency/scalability HTTP/2 benchmarks because they leverage zero-copy in the runtime.
Anyways, sexy terminal graphs with smag to enjoy!
submitted by /u/joesuf4
[link] [comments]
 | Lessons learned: A) Performance freaks to stop using #rstat 's runif for random generation. The Hoshiro random number generator arxiv.org/abs/1805.01407 is 10x faster. Implementations in #perl 's #PDL, #rstats (dqrng) and #python #numpy are within 20% of each other B) But does it make a difference in applications? To get to the bottom of this, I coded a truncated random variate generator in #rstats and #perl using #pdl (as well as standard u/perl) using the #GSL packages metacpan.org/pod/PDL::GSL::CDF & metacpan.org/pod/Math::GSL for accessing the CDF & quantile functions. In this context, it's the calculation of the #CDF that is the computationally intensive part, not the drawing of the random number itself. C) I should probably blog about these experiments at some point. Note that #pdl (but not base #perl) are rather competitive choices for large array processing with numerical operations. I mostly stay away of #python , but would not surprise me that for compute intensive stuff (where the heavy duty work is done in C/C++), it does not matter (much) which high level language one uses to build data applications preview.redd.it/qn00sx78gbuc1.… preview.redd.it/4by4jbh9gbuc1.… submitted by /u/ReplacementSlight413 |
Hi, im working on this perl script wherein i should get all files with filename < 900000
Ex. sample_file_802856.txt sample_file_27364692.txt sample_file_385620.txt
the script should get:
sample_file_802856.txt sample_file_385620.txt
I already have the code but it’s failing on this part coz im having a hard time getting the regex for < 900000 😆
submitted by /u/advinculareily
[link] [comments]
Hi,
I am moving to RedHat 9 from RedHat 7. I am running Apache with mod_perl.
I have installed the mod_perl package on the RedHat 9 box. I am getting this error on bit of code that I wrote:
Can't locate XSLoader.pm: /usr/local/lib64/perl5/5.32/XSLoader.pm: Permission denied at /usr/lib64/perl5/vendor_perl/Apache2/XSLoader.pm line 22.\nBEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/Apache2/XSLoader.pm line 22.\nCompilation failed in require at /usr/lib64/perl5/vendor_perl/Apache2/Access.pm line 24.\nBEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/Apache2/Access.pm line 24. When I do a search for XSLoader.pm, I find:
/usr/lib64/perl5/vendor_perl/APR/XSLoader.pm /usr/lib64/perl5/vendor_perl/Apache2/XSLoader.pm /usr/share/perl5/XSLoader.pm I am guessing I have some path issue. Any ideas what I may need to do?
thank you
submitted by /u/OrganicStructure1739
[link] [comments]
