Seems I have kinda drifted far from my original intent of all this blogging get a useable version of my Database::Accessor module out on CPAN. Though the last little while has been a very good learning experience for me it is time I get back on track to make sure I get a version out by Christmas.
In my first round of Moose-Pen post I gave a good example of how test driven development really does work well. The very short cycle of write a small test for requirement, write a little code, pass the test, reactor the code if needed and rerun test, it you pass out start the cycle again.
I also spend a good deal of time getting into Dist::Zilla and in this round of coding I am going to see how add in a little Dist::Zilla and Pod::Weaver to start along with my test driven development works out.
That moment when your auto-scaling, self-healing servers and continuously integrated and continuously deployed codebase all start working together seamlessly and flawlessly.
If none of that made any sense to you, then just understand this:
muhahahahah! *rubs hands together while laughing maniacally*
We’re doing a survey for the entire Perl community to find out some specifics and peculiarities about Perl and more importantly, about Perl developers. The survey itself is meant to gather some perspective regarding how developers are using Perl, where are they using it and how Perl is used with other technologies. This is basically a State of Perl in 2017 survey.
The survey will be open from the 7th of March to the 14h of April.
Please share it within your local Perl communities, every answer counts and makes this survey more relevant. The results will be available for the entire community to see, we will publish them the following week after the end of the survey. The data acquired through this project will show just how Perl is used and how the developer community is presenting itself at this point in time. It has 31 questions and it covers personal programming preferences, employment facts, geographical criteria, community events, tech stack data and more.
This is a great opportunity to capture the state of Perl as a language and as a community.
10:26 < kd> me: "how do I integrate the REST API with our psgi/mod_perl abomination?"
10:26 < kd> colleague: "aah I've been wanting to do that for a while, do you really need it?"
10:26 < kd> me: "yeah it would be good"
10:26 < kd> [waits two days]
10:26 < kd> colleague: "here, have a code review"
10:29 < kd> meanwhile it gave me the opportunity to prototype an important thing via a semi-abomination that would never be acceptable in production. So 1. We got a feature we really needed, and ensures the longevity of the platform, and 2. I got to do the important thing of getting my thing wrong on the first try.
I am happy to announce the initial release as an independent application of Camel Doctor - a simple HTML user interface for the default Perl debugger implemented as a Qt 5 executable. The debugger output is displayed together with the corresponding syntax highlighted source by a small formatting script. Syntax highlighting is achieved using Syntax::Highlight::Engine::Kate CPAN module by Hans Jeuken and Gábor Szabó. Camel Doctor is an implementation of an idea proposed by Valcho Nedelchev and provoked by the scarcity of graphical interfaces for the Perl debugger. Camel Doctor was started as a part of Perl Executing Browser in 2014.
As usual, any ideas and feedback are quite welcome!
CPAN modules are normally distributed with Makefile.PL or Build.PL,
so that people can install them by
> perl Makefile.PL
> make
> make test
> make install
This makes CPAN modules installable without any CPAN clients help
unlike other programing language ecosystem (such as ruby(gem), node(npm)).
On the other hand, today, people mostly use CPAN clients (such as CPAN.pm, cpanm) to install CPAN modules.
And it seems that when CPAN modules are not "complicated",
CPAN clients easily expect how to build/test/install them
even without executing Makefile.PL or Build.PL.
Now we have the concept Static Install.
That is, if CPAN modules are not "complicated" and set x_static_install 1 in their META.json,
then we may install them statically.
The first post of many looking at the various section plug-ins that are left over. The [Avaliability] plug-in is one works closely with Dist::Zilla and I also left you hanging with a problem I was having.
Well still suck in the [Availabillity] plug-in but I did find a bug which I patched locally and got the plug-in to work correctly for me. I think that is the second bug, well maybe 1.5 bug I have found since I started playing with Dist::Zilla.
OK, the tag “worst
Perl” might be overstating the case, but we ran into a funny error message
yesterday from a program that runs on all of our production equipment.
As each lot is tracked into a piece of equipment, the program running on it contacts our MES (manufacturing
execution system) to verify information about the lot. Because the MES used to
run on a really slow server, timeouts were common, so at some point the function
to look up a lot was wrapped in a function to retry a few times in that event. The MES server has since been upgraded, but we never took out the retry functionality. Here's the code in question:
In my previous post I explained how many utf-8 related issues are now fixed in the latest DBD::mysql development release, and I asked for feedback and testing from our users.
Even better utf-8 handling
I'm happy to inform you that, thanks to your feedback, we've now released yet another development version, with even more UTF8 issues fixed. Tanabe Yoshinori reported that column names and database warnings were not properly encoded and prolific contributor Pali Rohár fixed that issue, and much more.
Serialization issue under taint mode
One other issue which was reported by amavisd users has to do with how perl stores values internally under taint mode, which is the default way amavisd is run. This is now fixed, see for more information https://github.com/perl5-dbi/DBD-mysql/issues/78.
In this post I decided to dig deeper into the Pod::Weaver template well really I just explain that the 'weaver.ini' file is the template/
Dist::Zilla On Style
This post I go a little deeper into the varios differnt template bundles out that and show the template works a in a little more depth.
Dist::Zilla Takes it in the Name
The first in my rathder long series of review of the various 'Section' plug-ins. To start the rather simplistic [Name]
Dist::Zilla Regional Report
This post deal with one of the more common section plugins [Region] and I intoduce the concept of moving stuff about and build an ordered document out of an bunch of unorded parts.
I'm currently running slightly behind the schedule outlined in the grant. I expect to complete the Action Plan and have it ratified by other core members by March 18th, which is the date of the 2017.03 compiler release. Then, I'll implement all of the Action Plan (and complete the grant) by the 2017.04 compiler release on April 15th. This is also the release the next Rakudo Star distribution will be based on, and so the regular end users will receive better IO there and then.
This time on blog I'll show you how to write your own template engine - with syntax and behavior tailored for your needs. And we'll do it in four different ways to analyze pros and cons of each approach as well as code speed and complexity. Our sample task for today is to compose password reminder text for user, which can then be sent by email.
Another less than insipred day here at the Dist-Pen.
Well ten more posts to look at.
Dist::Zilla Plan
In this post I sat down with my Database::Accessor code base and ran it though dzil test to make sure it was all working.
Very Little Dist::Zilla
Well went off on a tangent with this post. I had problems with this test case 31_elements.t and finally found a solution to the problem I was having was where to place some test classes so the tests would run without hard-codeing the paths.
Dist::Zilla Party Time
Well in post I finally mad a mile-stone in my porject, I got all the test cases to pass and I found another bug I fixed and my tests still passed.
Dist::Zilla is Sad or is that Happy?
Still stuck on the same bug but this time I actully found a better solution that got rid of a kludge I was using and did not like
Hello everybody,
this is my first post, so please go easy on me.
I work with Perl for last 19 years and it always treated me extremely well in regards of interesting work or material compensation. Past December my company decided that it's time to finally join in the fashion of the day and start experimenting with ML.
I started researching and found out that's my lovely Perl is stuck in the past in regards to ML support and there's no any recent developments in this area (like full last decade).
Now look at Python!
Tensorflow, MXNet, Keras, Theano, Caffe, and many, many more. Java has it's deeplearning4j, Lua has Torch and what had Perl ?
We had AI::FANN, the interface (good one, I used it, it's good) to the C lib that has not seen any real development since 2007, only feed-forward neural networks, no convolutional networks, no recurrent networks, all advances in last 10 years just were happening outside of Perl.
Thanks to The Perl Foundation and our beloved sponsors, a large portion of the critical contributors to the Perl 5 Porters (p5p), the core group of Perl 5 developers, were able to get together on November 11th, 2016 at the Booking.com headquarters in Amsterdam, The Netherlands, for our very first Perl 5 Core hackathon, nicknamed Perl 5 Hack.
(Graphics credit to Leonardo Maia.)