blogs.perl.org

Just a quick reminder to those of you that would like to benefit from the early bird price for the upcoming YAPC Europe conference that will take place in Granada the first week of September: purchase your ticket by May 15th.

See full details on prices and dates.

I must be doing something wrong. Surely. I have a REST service. I get data using HTTP::Tiny and use JSON::Tiny to decode it.

If I try to print to the Term::ReadLine::Gnu OUT filehandle, I get double encoded strings, like this:

    coração

If I try to binmode it to utf-8, things get worst, with triple encoded strings:

    coração

Resolved it decoding (Encode::decode) from UTF-8 and using the internal Perl character representation. It worked.

The problem was when I tried to feed a pre-defined input line to Term::ReadLine::Gnu. Result looked something like this:

Hi,

Did you see that the brand new code editor just released by Microsoft (https://code.visualstudio.com) ships with the Perl 6 syntax support?

As promised here is the list of CPAN distributions for the Mini CPAN PR Challenge at the
NYC Perl Hackathon 2015.

Mini CPAN Pull Request Challenge Distros

If you are attending the hackathon and participating in the challenge please add yourself to the wiki page as a participant.

At the previous QA hackathons, I spent most of my time on improving various aspects of CPANTS. However, I usually couldn't see what I implemented there online, because it takes about a day to analyze everything. All I could do was to start the analyzer before I fly back and confirm the result at home.

This year, things went differently for me. I spent three days on porting PAUSE Web UI using Plack toolkit, and was able to actually see the result there.

Why ported?

..because I didn't include mysql utf8 cruft in a connection string in something.

Thing is, I've done tonnes of localisation, from parsing named entities in german, to dealing with misconfigured mysql databases, localising currency, numbers and dates to dealing with special cases of greek capitalisation in pattern matching.

So for future reference, if you're relying on connection strings client side, you're doing it wrong - that's brittle and will eventually fuck up when somebody forgets to do it or uses a dodgy my.cnf - instead force it at server side and don't risk messed up encoding : http://blog.oneiroi.co.uk/mysql/mysql-forcing-utf-8-compliance-for-all-connections/

You're welcome

I'm happy to say that I'll be participating in the 2015 New York Perl Hackathon. I'd like to thank Bloomberg, L.P. for sponsoring me so that I can attend this event.

While I'm at the hackathon, I hope to continue my work on MetaCPAN as I did at the QA Hackathon one week ago. I've put together a list of possible MetaCPAN projects. If anyone would like to take on any of these projects, feel free to get in touch with me in advance if you have any questions on what might be involved with any of these proposals.

I'll also be available to help out with things which aren't MetaCPAN-related: Perl, Git, GitHub, etc. There's more general information at the hackathon wiki.

I will, of course, report back on my progress at the hackathon after the event has taken place. I'm looking forward to a productive day of hacking with a group of smart, motivated people.

The German Perlworkshop takes place next week, Wednesday to Friday, May 6th - 8th, 2015 in Dresden, Germany.

Hurry now while stocks last!

Schedule: http://act.yapc.eu/gpw2015/schedule

In brief, SiteSuite have agreed to host on the 14th of May.

Dates beyond that are up for grabs, and speakers are welcomed for any and all meetings.

Help promote by printing and hanging either the A3 or A4 poster around your workplace, university, college, local hang outs etc. but please ask for permission before hanging them!. Other PM groups are welcome to use them if they seem useful.

More details to come, or subscribe to Sydney-PM mailing list

I recently read an article about Aha! – A Hacker’s Assistant, a superoptimizer used to find branchless algorithms with brute force. There's a problem for which I always wanted a short branchless solution: finding the length of a UTF-8 byte sequence without a lookup table. So I gave Aha a try.

The length of a UTF-8 byte sequence is determined by its first byte. The possible sequences are:

• 1-byte sequences start with a byte in the range 0x00-0x7F
• 2-byte sequences start with a byte in the range 0xC0-0xDF
• 3-byte sequences start with a byte in the range 0xE0-0xEF
• 4-byte sequences start with a byte in the range 0xF0-0xF7

(There are a couple of other restrictions but I'm only interested in valid UTF-8 strings and don't care about the results for invalid sequences.)

I too was among the crowd that attended the Perl QA Hackathon 2015 in Berlin. Here's my report.

After looking at today's issue of Perl Weekly, I remembered of a nice advice by MJD that basically boils down to: make faces look at the content, or at least not look away from it.

My photo loaded on Gravatar was looking towards the right, which is good when your photo is put on the left of the page, but a disaster when it's placed on the right (which is what happens on Perl Weekly and here on blogs.perl.org, by the way).

The fault is totally my own: the general photo that might end up anywhere SHOULD look at the camera, so that it will be at least neutral in the general case! I changed it of course, even though I'm not sure I like the results... time passed!

One week ago I was in Berlin at the Perl Quality Assurance Hackathon (QAH), happily hacking away on MetaCPAN. Today I'll summarize the good, the bad and the ugly about my time in Berlin. Spoiler alert: it was all good.

The full post is here.

Hi everyone,

I am proud to announce another release of Dancer2, carrying many changes and improvements, with 9 contributors and 21 tickets closed[1].

This release carries the following major changes:

* Workaround for multiple plugins with hooks.
* "send_file" is asynchronous by default. Fallback to synchronous.
* "prefix" now supports the entire route path spec ("/:var" now works in prefix).
* Clear up prefix inconsistencies ("/var" vs. "/var/").
* Proper package reported in logging.

The QA Hackathon wouldn't be possible without the support of all of our generous sponsors. In this post we cover the sponsors not previously thanked here, including the individual members of the Perl community who made personal donations.

You can read about some of the things done at the hackathon in the blog posts, linked off this page on the QAH website.

Hi guys,

Let me announce my new Perl related site devoted to all the Perl books ever published: allperlbooks.com.

This is a collection of the Perl book covers, primarily from the private library of Liz and Wendy. You might have seen these book shelves at the Perl booth at FOSDEM or at one of the Dutch Perl Workshops.

I would be very appreciated if you will share more Perl book covers with me, my main interest is non-English books (maybe except Russian ones as I have a few dozens of them, and probably almost everything which was published in this language).

For the funny part, here's the page where you'll find a pearl on the book cover :-)

Feedback is also welcome.

yeah me too ....

Or lets call it insights from an imposterer. I just came because I like the people and I could visit my brother and maybe Berlin art galleries. (which I did). I knew the place because German Perl Workshop two years ago was here too. So i could show people the way to the pub when they left work from day one I just came from train station and could immediately say hai to ingy - perfect.

You might be overwhelmed by all the reports about the QA Hackathon. I am impressed and thankful! I just wish each report had a different title :).

I am especially grateful for the people who have collected the posts. It's much easier now than next year when someone will look for justification to attend or sponsor the event!

I was at the QA Hackathon in Berlin this year.

Everyone else writing about it has an introductory section about what it is, so I needn’t concern myself with one… as well we’re on blogs.perl.org here after all.

In a stupid move, I forced myself to constantly look for some other hacker to mooch power from – I left my own power supply at home. Fortunately as a semi-reluctant initiate to the Apple cult, I found plenty who were of the same hardware persuasion, whom I could bum some laptop juice of life from. I hope to not repeat this part.

But the main reason that I chose to be present at all was for the consensus discussions scheduled this year.

I published a new article about Perl in my blog. It's about wrapperl, a wrapper for Perl customized invocation. Find the article here and happy reading!