blogs.perl.org

I try postderef in Perl 5.19.5. The following code don't work.

my $params = {
  foo => 1,
  bar => 2,
  baz => 3
};

my $new_params = {};
$new_params->%{'FOO', 'BAR'} = $params->%{'foo', 'bar'};

I expect {FOO => 1, BAR => 2}.
But left side assignment don't work. Is this specification or bug?

posted by @cruxacrux at http://habrahabr.ru/post/198274/

The announcement for the call for speakers has just been posted to the YAPC::NA official blog and Twitter feed.

This year the theme is “¡Viva Perl!”. Talks that embrace the theme will be favoured by the orgas. when deciding which submissions will be presented. remember that there are a number of tracks over several days, there is a great deal of room on the schedule. It also is apparent that the organisers are keen for people to come to them early with ideas of talks, meetings and events they want to run to coincide with the conference.

As with any Perl event the barrier for entry is set purposefully low, we like to embrace neophyte Perlers and conference attendees and give them the chance to not only attend but to participate. Perl has a very supportive community to new speakers.

I am looking forward to seeing the talk submissions start to fly in: http://www.yapcna.org/yn2014/newtalk

Contact the orgas at: talks@yapcna.org

MarpaX::Languages::SVG::Parser uses XML::SAX and Marpa::R2 to parse an SVG file into an array of hashrefs.

XML::SAX parses the input file, and then certain tags' attribute values are parsed by Marpa::R2.

The attribute values treated specially each have their own BNFs. This is why it's called nested parsing.

Examples of these special cases are the path's 'd' attribute and the 'transform' attribute of various tags.

The SVG versions of the attribute-specific BNFs are here.

You are encouraged to peruse the FAQ.

I hope this code will show that it is not really difficult to implement 2-level parsing of (e.g.) XML for any dataset.

I list shortage of Perl.

• Object-Oriented feature in core

  For a long time, Perl don't support clean Object-Oriented feature in core. Ruby and Python can write OO programing clean, but Perl can't. This will be resolved by adding mop to core in the five years.

• Web application

  Perl don't have famouse Web application. For example, PHP have Word Press, phpMyAdmin, Python have trac, Ruby have redmine, GitLab, but Perl don't have. I think we need to see web world.

• Web service startup

  People think Perl is old language. If people contine to think this, People tend not to use Perl in web service startup. Now Perl have Mojolicious, Web startup is easy and clean. Perl disadvantage is none compare with Ruby on Rails. We can recommend Web service startup with Perl.

• Statistics

  age is attending to big data and staticstics. In this area, most people maybe select R language and Python numpy and scipy. Perl have PDL, but I think most people maybe select R langauge and Python numpy and scipy. These are more clean and simple than PDL and Perl. People tend to select clean and simple interface. I want clean staticstics library.

Perl comunity tend to attend to CPAN and Perl language itself,
but I think we need to see the outer world of Perl itself and CPAN.

I wrote a little article on how to structure larger Dancer applications. You can find the article under:

http://fraley.de/2013/10/18/structuring-larger-dancer-applications/

Hope this is of help for someone.

At times, it is desirable to access any file on your box. Forgot to put it on dropbox? Then what do you do? Enter FileBeagle. It is your own personal cloud and written in Perl and Mojolicious. The install is copying one file onto your box and running the executable. The only other file that is permanent is the database that is created.

There is currently a Lite edition with a Pro version coming soon. The Lite version is free.

Do you get tired of reading a man page, or even
perldoc, for cryin' out loud, and having to deal with the
POSIX regex engine instead of something more powerful and Perl-like? I
know I do. Every time I type /^[[:space:]]+something,
instead of /^\s+something, it just makes me sick. Something
ought to be done about this nonsense.

Well, after saying something like this to myself for the umpty-jillionth
time, I decided to look into it.

I did an internship for Moose as part of GNOME's Outreach Program for Women. I was supposed to convert all stringy exceptions in Moose to structured exceptions or exception objects. This is my first major contribution to a FOSS project :).

Code
This is my merged pull request (a bit late, but better late than never).

Diff stats
If you're interested, then you can check out diff stats here. Caution : You may get lost in that big stats, so better not to click on that URL ;).
In short :
368 changed files with 23,830 additions and 1,479 deletions.

• Modern Perl Book
• Moose documentation
• The Art of the Metaobject Protocol
• Introduction to Moose by Dave Rolsky
• Role Usage Patterns
• Introduction to Moose by Shawn M. Moore
• Extending Moose for Applications
• Exception handling slides by John SJ anderson
• Apart from above, my mentors & people on #moose and #moose-dev on irc.perl.org were extremely helpful

I translate Perl Tips to English.

Perl Tips - Perl Tutorial by Code Examples

Perl have several easy to wrong points. If you use something of them, Perl programming will become smooth.

I've been contemplating to do something like this for a while, but have only gotten around to it today. Here it is: SHARYANTO-Shortcuts-0.01.tar.gz. So far it's only hosted on github: http://github.com/sharyanto/releases-perl-steven (BTW, I also archive my CPAN releases there: http://github.com/sharyanto/releases-perl-cpan). The release is just a distribution that contains shortcut modules like DD (shortcut for Data::Dump), DDC (Data::Dump::Color), etc. The dist is not put on CPAN for obvious reason: the modules will terribly pollute the top-level namespaces.

With the current toolchain we have in Perl today, deploying non-CPAN modules should be easy enough.

My point for this post is that I think there exists a niche market for a platform that hosts non-CPAN releases but reuse the CPAN tools/architecture. Either private/commercial modules (the so-called DarkPAN), personal forks (e.g. I can have my own JSON::XS, there can be multiple modules with the same name from different author like on github), or things like what I published today (modules that do not comply with CPAN naming rules/convention).

When adding a new entry to the new Perl TV site, I copy some of the data from YouTue itself. To make it easier I wrote a small script that fetches the data from YouTube using the WebService::GData module.

Unfortunately, staring from perl 5.18 the module started to emit lots of warnings. The original author did not have interest furher maintaining the module, but he was kind enough to give me co-maintainer bit. A new version (0.06) is on its way to CPAN.

If you are using this module, I'd be happy to get your help in testing and further improving it.

Er, an earlier version of this said the software bug was 20 years old. It's 30! Thanks, Sidhekin

Today, in reading some data, I processed 36,916 potential dates. Two of those 36,916 failed to validate. I wasn't terribly concerned as these dates come from client-supplied data and this data is often, um, surprising. However, when I inspected the raw data, it turns out that those dates were January 1^st, 2011 and January 1^st, 2007. I had a bug in software I wrote about a month ago, but it turns out that this bug is actually 30 years old.

For anyone who doesn't really understand the software ecosystem, this may sound mystifying, but it makes sense. Because of a decision taken a long time ago to make another company money, my $client lost money in paying me to fix a bug that one company accidentally introduced and another company deliberately introduced. But to explain it I need to talk about a third company that introduced a feature that eventually became a bug, and a few other historical tidbits that nonetheless contributed to the obscure bug I fixed today.

For my presentation to the Houston Perl mongers tonight, I'm talking about Randal Schwartz's regex to parse JSON.

% perl -ne'next unless /^perl/; 
while (/ -[Mm](\w+(?:::\w+)*)(?:\b|=)/g) { $mods{$1}++ } 
END { for (sort {$mods{$b}<=>$mods{$a}} keys %mods) { 
    print "$mods{$_}\t$_\n";
}}'  ~/.bash_history

Here are mine (top 20 on my laptop):

I slid into the world of eBooks when a half-price Nook sale collided with O'Reilly's
Day against DRM half-price sale. It was the Perfect Storm that this tight-fisted Luddite needed to take the plunge. I set myself a budget and just as I'd picked out all the books that I allowed myself, O'Reilly decided I'd bought enough to merit a 60% discount, so more books had to be bought. One must stick to the budget!

PubMed is experimenting with ePub formats and they are much easier to read than the customary PDF's, but waiting for everything to be converted (or just trying to find one) would try the patience of even Vladimir.

I have a suggestion for someone with more Impatience than me. (I started this post 5 months ago). Have a look at LaTeXML and then think that with many of the papers submitted in LaTeX and a tool that converts to XML, you're halfway to reading all your latest science down the coffee shop.

I've recommended Disastercast here before, and I know that some of you have since subscribed. However, for those that haven't, episode 13 is worth listening to. It is about safety issues arising from software, in particular looking at the Therac-25, a medical device which which, because of race conditions, killed people.

(Hopefully this post will become outdated soon...)

        https://code.google.com/

        https://code.google.com/hosting/

I had a recent discussion with a Data::Dump::Color user about formatting ints/floats/stringy numbers differently. So here's a short summary of how core module function Scalar::Util's looks_like_number() can be used to detect the different data types:

UAV::Pilot version 0.6 is now on CPAN. Lots of little changes this time. The big thing is an API change, where Control::ARDrone and Driver::ARDrone were instead named ARDrone::Control and ARDrone::Driver, respectively. This keeps everything related to a single type of UAV under one namespace directory, which I think will be nicer going forward as I implement other UAV systems.

[More on my blog]