Do not ask what Perl can do for you, ask what you can do for Perl!
In my effort to bring the new signature back to older versions of Perl, I'm
maintaining Filter::signatures,
a source filter that simply converts the signatures to the equivalent old-style
Perl code. That filter works surprisingly well for its simplicity and has caused
very little in problems.
This is the third article in a series on CPAN distribution metadata. The first article was a general introduction, and the second article looked at dependencies, and in particular the different phases that you can specify dependencies for (configure, build, runtime, test, and develop). In this article, we'll cover the different types of dependencies and how you combine these with the phases (described in the previous article) to specify the dependencies (or prereqs) for your CPAN distribution.
This article is brought to you by MaxMind, a gold Sponsor for this year's Toolchain Summit, being held next month (May) in Lyon, France. The summit is only possible with the support of our sponsors.
Hello all,
In my first blog post I've announced AI::MXNet, Perl interface to the MXNet machine learning library.
The eight weeks that passed after that were quite fruitful, I've ported whole python's test suite, fixed multiple bugs, added docs, examples, high level RNN interface, Perl API docs has been added to the official MXNet website.
This time I'd like to review in detail three examples from the examples directory.
First one is a simple calculator, a fully connected net that is structured to learn
four basic arithmetic operators: addition, subtraction, multiplication and division.
Second example is a comparison of two different approaches to the task of classification
of handwritten digits, and the third one is an example of LSTM RNN network trained to generate Shakespeare like text.
Here is the image (generated by
Graphviz
) of the calculator network.
The data input is two numbers, that are being routed via two paths; first path is turning the input values into natural logarithms and feeds these into one neuron sized fully connected layer.
So after
yesterday's
little review I finally got to do some coding on Driver::DBI and the first thing I got working was my '00_load.t' test case. All I needed to do with the present sate of the code is add in;
my $in_hash = {
++ da_compose_only=>1,
view => { name => 'name' }};
to that test case and the error I was getting from DBI;
BD::ExampleP::db prepare failed: Syntax error in select statement ("1") at
went away. Now the error was caused by this sub in Driver::DBI
In January this year, I got Jemplate in the CPAN Pull Request Challenge. The module implements Template::Toolkit in JavaScript, so you can transfer the burden to process the templates from the server to the client.
One of the open issues in its GitHub repository caught my attention: Jemplate compiled all the templates coming from different files into one large JavaScript code-block. If you declared two blocks with the same name in two different files, they’d end up in the same hash in JavaScript, and only one would survive—but you couldn’t tell which one. Keeping block names unique across files probably isn’t part of common practice, so making the module warn you in such a case sounded like a reasonable requirement.
The Perl Conference this year is going to be in the DC-Metro area, specifically in Alexandria, VA at the United States Patent Office. We've got some great talks lined up and are continuing to update the schedule at http://www.perlconference.us/tpc-2017-dc/schedule.
Register and reserve your spot to listen to speakers like Damian Conway, Mark Jason Dominus and Sawyer X to name a few. You can purchase tickets for our event and/or the tutorial sessions here.
The local PM groups (DC and Baltimore) are really excited about hosting this year's Perl Conference. I hope to see you there.
Yesterday I summed up what I was up to over the past month or so since I left the Dist-Pen, So tadoy as I am rather sort on time I will just do a quick post-ette on the state of Database::Accessor::Driver::DBI.
Well just for kicks before I revisited any of the Driver::DBI code I re-ran the the very limited test suite of two test case and got a full fail, so I guess every thing is broken.
Looking at the code the first think I noticed was that I have this sub
sub _warn {
my $self = shift;
my ($message) = @_;
warn("Database::Accessor::Driver::DBI: $message ");
}
Which I was using to key of this DA flag 'da_warning' now what I think I will do is hop back to 'Database::Accessor::Roles::Driver' and add this in
I don't mind working with Spreadsheets. Much of my work consists of creating
Spreadsheets from SQL queries. Sometimes, the resulting spreadsheet should be
a pivot table, listing some values across the spreadsheet. For most of my
Spreadsheet-generation needs, Querylet
is sufficient, but it cannot create pivot tables.
As proposed to and approved by the Grant Manager, I've extended the due date
for this grant by 1 extra month, in exchange for doing some extra optimization
work on IO routines at no extra cost. The new completion date is May 22nd;
right after the next Rakudo compiler release.
Communications
I've created and published three notices as part of this grant, informing the
users on what is changing and how to best upgrade their code, where needed:
Now that I am finally finished with Database::Accessor for the moment as since my last post all my tests are passing, I think it is time for a quick recap of what when on since this post when I left the Dist-Pen and started up the Moose-Pen.
The first few post I set out on writing my first Driver::DAD, I worked out some name-space issues and finally came up with Database::Accessor::Driver::DBI rather than SQL as most DBI drivers run on SQL is just seemed locgial.
The second set of posts I started to write up my Driver::DBI and ran into the problem very quickly that I needed some sort of DBI DB present on the current box to do any testing. I solved this as 'DBD::DBM::db' comes with DBI so I decided to use that for my testing. I even got one or two test cases written and a little code done.
I recently added some functionality for random number generation to my modules, which led me on a digression about rand(). This is a short look at some modules for getting random floating point values. A later one will look at random ints and bytes.
I left off from yesterdays
post
with few more tests to clean up and a new one or two to write up. Might as well get the low hanging fruit first and that is this error;
Can't locate object method "dynamic_conditions" via package "Database::Accessor::Driver::Test" at 43_dynamic_conditions.t line 54.
and the change was a very easy removal of that 'dynamic_' from the test;
The Perl Toolchain Summit (PTS)
is the annual event where we assemble the people who are actively working on the Perl toolchain, and give them 4 days to work together. In this blog post, we'll look at how we decide what everyone will work on, and give you a chance to make suggestions.
This blog post is brought to you by Perl Jobs by Perl Careers,
which as well as helping Perl programmers find jobs, supports a number of community events, including the QA Hackathon last year.
Autoload can be a very powerful tool in Perl, though often you should first consider if there's a better way; Autoload is not necessarily the best solution for cases where you just need to generate many methods by name, and definitely is not the best solution for "wrapping" static methods. But if your use-case does necessitate methods created on the fly, I have released Autoload::AUTOCAN to make this easier to get right.