but this time round I got a full pass but I was plagued by warnings like these.
Use of uninitialized value in array element at /home/scolesj/database-accessor-driver-dbi/lib/Database/Accessor/Driver/DBI.pm line 803.
Use of uninitialized value in numeric ge (>=) at /home/scolesj/database-accessor-driver-dbi/lib/Database/Accessor/Driver/DBI.pm line 802.
A trial release of Dancer2 (0.206000_01) was just uploaded, and should be available on your local mirror soon. This release addresses some couple of potential security exploits, and could use some scrutiny prior to an official release.
Please see the release for the full list of changes.
There will be a coordinated Dancer/Dancer2 release in the near future with more detail. In the meanwhile, the more eyes on this, the better. Please leave us your feedback through the usual channels (IRC, email, github, etc.).
The following is not a blow-by-blow (painful and uninteresting to
read), but rather what I came up with after a few false starts,
with emphasis on what I did over and above the Test-SmokeREADME
documentation, and (sometimes) why.
Environment:
macOS 10.13 High Sierra
Custom-built Perl installed system-wide in custom directory
CPAN client (not cpanp or cpanm) configured to sudo
Yesterday, I attended Gotanda.pm, which is a Japanese local pm group organized by karupanerura.
A lot of interesting talks were presented there.
I especially enjoyed codehex's talk, where he introduced how to write closures in XS.
You can read his blog post for the more detailed explanation.
And I gave my talk about writing perl with w0rp/ale, which is an Asynchronous Lint Engine for vim8.
There is already a blog post about it by oalders, so you may notice it.
If you write Perl with vim, why don't you try ale together with
my simple syntax checker skaji/syntax-check-perl?
A few weeks back, it was pointed out to me that Timm Murray was proposing to write an eBook for using Perl on the Raspberry Pi. Due to my extensive work on that platform over the last two-plus years, I had keen interest in the project.
Timm will be writing the bulk of the content using various distributions including my RPi::WiringPi along with all its related distributions, and I will be adding at least one chapter to cover my indoor grow room single-webpage environment controller, as well as performing editing duties and testing of the code.
We've been working together for a couple of weeks now, and today, I'm proud to announce the official launching of the fundraiser for the new book.
Whether you're interested in working on the Raspberry Pi, or just want to donate to a good cause for other Perl hackers, please have a look.
of my tests from
yesterday
. Remembering to stick in that 'id' in the values to be inserted will take away from utility of my API. Needless to say that sending an empty value for an create/insert is confusing at the least and downright disturbing to some. Therefor I will have to make this revised test;
VM (aka Vicky) spent most of her 20 years in the tech industry leading software development departments and teams, and providing technical management and leadership consulting for small and medium businesses. Now she leverages nearly 30 years of free and open source software experience and a strong business background to advise companies about free/open source, technology, community, business, and the intersections between them.
She is the author of Forge Your Future with Open Source, the first book to detail how to contribute to free and open source software projects. Think of it as the missing manual of open source contributions and community participation. The book is published by The Pragmatic Programmers and is now available in an early release beta version. It's available at https://fossforge.com.
Last Thursday, I attended the London Perl Mongers Tech Meet at the Zoopla. This was my second time attending tech meet. I must say this was better than the previous meet, in many ways. First there were more people this time than compare to the last one, I attended. Second, this time talk was more Perl-ish. And last but not the least, plenty of food and drinks, thanks to all the sponsors.
I just shipped 1.300 of this module to the CPAN and it occurs to me that I’ve never talked about it here. I suppose I figured that what it does is so simple that there’s not much to say about it. But it‘s useful if you need what it does, and I wrote it because nobody else had.
Do you have a web site being served over HTTPS?
Do you want to redirect visitors coming in over HTTP to HTTPS? (I.e. send visitors of http://example.org/some/where to https://example.org/some/where instead.)
If you answered yes once, you almost certainly answered yes twice. Right? It’s such a common thing to need.
But when I went looking for a way to make my PSGI application do that, I found nothing on CPAN.
This new section introduces the XML::LibXML::Reader API which is a pull-parser style with much lower memory overheads that a traditional DOM parser. It also covers hybrid operation where the Reader API is used to scan through the document and extract sections as DOM fragments for further interrogation via XPath.
ANTLR4::Grammar lets you convert ANTLR4 lexer and parser grammars from ANTLR to Perl 6. It currently works with all of the basic EBNF constructs, and for the moment chooses to ignore the features of ANTLR that the native Grammar type doesn't support. When I've added the basic Action class I'll probably add support for ANTLR4 modes. ANTLR4 types make a bit of sense as they've at least got string and int types, but actions don't make much sense as if you're using the tool, you're likely porting an existing Java- or C-based grammar over to Perl 6 and the existing Java code wouldn't make sense.
Future additions include automatically generating a basic Action class, and possibly enough code to build an object-only AST from the grammar itself.
We needed to upgrade from EL6 to EL7 at work. After the upgrade, we noticed some of the JSONs returned from the APIs had changed: some numbers were suddenly enclosed in double quotes, while some others lost the quotes, which broke customers’ code written in strongly typed languages (e.g. Java).
We used the system default perl to drive our web application, using libraries provided by the vendor. While Perl’s version changed from 5.10.1 to 5.16.3, the version of JSON::XS responsible for creation of JSON data jumped from 2.27 to 3.01. Both the changes contributed to the problem.