I am Yuki Kimoto, Japanese Perl programmer. I create tutorial site in Japanese and English. I create Perl module and upload it to CPAN. I create Web application in Github.
I recently updated File::Temp and wanted to standardize how we were creating temp files. Most places were using File::Temp already. I ran across one file where we using IO::File and returning both a file handle and the filename. I changed it to simply return a File::Temp object.
I rolled the change out to a test system and noticed a problem... All of our generated files were empty! I traced the problem down to using the File::Temp object with File::Copy's copy subroutine. I suspect it's the tied file handle bug biting us but the fix was quite simple.
Perl6 is at a turning point. Now running on 2 virtual machines (Parrot and JVM), with 2 more coming available in the next months (Javascript and MoarVM), with abstract concurrency on the JVM now and full Perl 5 interop at the horizon in MoarVM.
To make it easier for past, current and future Perl 6 contributors, we have asked Jonathan Worthington to give an intensive 2-day workshop taking a deep dive into many areas of the Rakudo and NQP internals. This is your chance to get up-to-date with Perl 6, specifically with Rakudo and NQP.
The workshop will mostly be focusing on the backend-agnostic parts but with coverage of the JVM and future MoarVM backends too. While the overall focus will be on getting to know the Rakudo and NQP internals, we'll also build the odd small language and object system along the way to get a better handle on the primitives.
It will be held in Frankfurt am Main, Germany, on 14/15 September 2013
Just as blog posts including images also documentation that includes images (even screenshots) is more plesant for the eye than just plain text. On both search.cpan.org, and Meta CPAN one can have images linked from the POD.
It would be awesome if more modules had a few images or screenshots included
and you can gain fame via the relevant Questhub Stencil.
Based on feedback, I've made a number of changes to how the adoption list is created. They're summarised below, and described in more detail on my blog. We've had the first release from an adoption prompted by the list: Stephen Nelson has released Convert-BinHex (+1 his quest). This prompted me to create a Hall of Fame. Let me know if you adopt a module, whether it was on the list or not.
Without knowing it, both Steffen Mueller and I released modules this morning related to using the Tiny C Compiler for compiling C code at runtime! I have tried to make a fuss about mine (as evidenced by my blog entry this morning), but neither of us were aware of the other. Hopefully we can combine forces. Steffen, of course, knows an aweful lot more about typemaps and the available typemaps module ecosystem than do I. I plan to contribute the energy and enthusiasm! :-)
My Alien module for tcc is on cpan and github, and my Perl bindings for libtcc are also on cpan and github.
There is one other module related to tcc on CPAN, called C::TCC. For better or worse, the module doesn't really provide a means for sending much to it, or getting much back from it, and the module author hasn't replied to my emails. Who would have thought that two folks would publish unlrelated modules on the same fairly unknown piece of software just over four years since the last thing to hit cpan?
Pushed Ouch 0.0404 to CPAN. It turns out I was using some Perl 5.10 and 5.12 features (use parent and use overload respectively) and that was causing some CPAN testers errors, and also problems for folks on old Perls. So I’ve made Ouch explicitly require Perl 5.12 going forward.
The CERT program at Carnegie Mellon University has created secure coding guidelines for several programming languages, including Perl. It is a community effort, and guidelines are written and discussed on a wiki-style platform.
Some of the guidelines are associated with Perl::Critic, so I've given my 2 cents on those. David Svoboda is the lead author for the Perl guidelines, and he has been very responsive to my feedback.
But I'm no authority on Perl security issues. I'm sure David would love to get some input from real experts in the field. So if you'd like to contribute to this important and highly visible resource, then hop over to CERT's Perl page and request an account.
There are many things you might do to speed up your Perl code. After profiling and benchmarking, you revise the slow spots, or maybe try a different algorithm. If you still need more speed, you may use Inline::C, or use PDL if you are doing numerics, or even write your own XS code. Reini Urban has even tried to create a Perl Backend that rewrites your Perl code as C code, and has even worked on a port of Perl5 to Potion.
But let's face it. Sometimes it would just be easier if you could write your code in C, and interpolate a string into it. Wouldn't it be nice if there was a C equivalent of Perl's string eval?
(this is the email sent to the Dancer users mailing list, updating on recent releases)
Hey,
we have just released a new version of Dancer 2: 0.08. While it didn't carry everything we had wanted (one specific change was left for 0.09), we decided it is more important not to delay features and fixes. We can also do another release next week, right?
This was the biggest Perl event I've attended so far.
Also, it was the first one I've attended outside of Brazil.
And I'm happy to see that there is so many people in Ukraine who are passionate about Perl!
So, listing some of my impressions below.
The supporting slides for the YAPC::EU lightning talk that I had in the first day of the conference are here:
Because the slides are just a few and the presentation was in a rush, I wrote a extended blog post regarding what is PRForge and how it can help the Perl community to increase its overall audience on my personal blog.
I've finally realized that instead of people worrying about false, or ever true, reports of Perl's demise, we can generate some factual (nice change!) data about Perl activity.
So, I'd like to see someone analyse the postings to the archive of modules at perl.org. See e.g.: