Sydneysiders are invited to join us this Thursday night for yet another Sydney-PM meet.
SiteSuite have offered to host us. Thanks to Cees for setting the wheels in motion for us to use the venue.
What: Sydney PM
Date: Thursday, 16th October 2014
Time: 6-9:30pm
Where: SiteSuite, Level 3, 1 Bay Street, Broadway Shopping Centre, Sydney
Who: Anyone with any level of experience with Perl. Please bring friends, family and co-workers!
The building locks it's doors at 6pm, so one of their staff will let us in. On the day a contact mobile number will be posted for stragglers. Please jump on the sydney.pm.org email list for that detail on the day.
Cees will be giving a talk about Rose::DB and we have a guest speaker giving us this talk live from San Francisco...
I released a new version of Pod::Readme yesterday. It's a module for "Intelligently generate a README file from POD" by using POD =begin/=end and =for commands to control what parts of a module's POD are included/excluded in the README. For example, you don't need the details of method calls in the README, nor do you need installation instructions in the module's man page.
This is a major rewrite using "modern Perl" that supports the following features:
Generating a README in various formats such as plaintext, POD, markdown, HTML;
Support for plugins to add new features.
Support for (via plugins) inserting the module version, recent changes and prerequisites in the README.
It should still work with existing software that uses it, such as Module::Build.
The next steps will be to write modules to integrate this with other release tools, such as Module::Install or Dist::Zilla.
Feedback as always would be appreciated. The module is on GitHub.
Thanks to everyone who commented on previous blog posts about this, and to CPAN Testers for test reports on previous dev releases.
Have you ever wondered which modules are currently loaded by current process? With Perl it's very simple to know this piece of info. Perl saves loaded modules in a hash %INC.
System on a Chip (SoC) devices, such as the Raspberry Pi and pcDuino, are becoming increasingly popular. They almost always have a working Perl installed, and some library for controlling the I/O pins. Wouldn’t it be nice to unify the API across devices? While we’re at it, why not add a REST interface, too? The Device::WebIO modules do exactly that, and this presentation will show you how to use them.
This is also the 20th anniversary of Perl. There is a rumor of cake.
Who here like me still uses Opera (specifically Opera 12 on Linux)? It's being abandoned, the bugs are piling up, and more websites are not rendering correctly on it. However, the combination of keyboard shortcuts and some specific features like editing+applying source code makes me still stick to it.
The Opera makers provide a service called Opera Link that can synchronizes your browser bookmarks and a few other stuffs between computers and mobile devices. However I prefer not to use it and rely on some good ol' tools instead.
I also happen to be a fan of Org so Org will be the master document.
The steps that I describe here might be too much of a hassle, but I like it and thus share it.
A couple of days ago I got a tip that I was very close to being the first CPAN author to upload 1000 releases in a year (989). Today I topped it off:
Thus ends my CPAN numbers ambitions. From now on I will concentrate on -Oquality-Ofun and -Oacmeism. Actually the numbers stuff ended in early September.
The -Oquantity and -Ofrequency flags were fun for a while, and it resulted in my getting a large portion of my modules into an up to date state; but numbers for numbers sake has a limited appeal.
Note: It was ironic that one of my final releases was from a pull request by SHARYANTO++ who leads almost all the CPAN statistics. :-)
($response->{reason} or '')) unless$response->{success};
my$ip= $response->{content};
chomp$ip;
$ip;
}
1;
__END__
It's a one file module, which simply contacts http://curlmyip.com, retrieves the content with HTTP GET request, and finally chomps the result; because there exists an extra new line character which is useless.
Elasticsearch has a builtin scoring algorithm which works quite well in practice, but sometimes you want to roll your own scoring algorithm. Let's examine how to create a custom scoring algorithm using the function score query.
Let's assume we want to search and score Perl job offers based on a set of weighted keywords. To get the score of each offer, we'll multiply the weights of matching keywords where positive keywords have weights greater than one, and negative keywords are weighted less than one. Thus, the positive and negative keyword matches add and take away from the final product (score) respectively.
Define the Qualitative Importance and Their Weights
Qualitative Tags
Instead of assigning weights directly to keywords, let's use qualitative tags of desirability (importance) for each keyword (trait). Borrowing from okcupid's five degree scale of importance:
mandatory
very
somewhat
little
irrelevant
This takes care of the non-negative traits, now let's add qualifiers for negative traits using a similar pattern:
I deal with a lot of modules that promise backwards compatibility with older
versions of perl, usually back to perl 5.8.1. Since I don't regularly use perl
versions that old when developing, accidentally introducing incompatibilities is
always a risk. Having a continuous integration system check this for me makes
it much easier to catch mistakes like this before they get released into the
wild.
Travis CI is a very useful continuous integration
service that is free for any public repositories on
GitHub. There are issues with using Travis CI for the
kind of testing I need though. First, it only provides the last revision of
each perl series. Especially in the perl 5.8 and 5.10 series, there are
substantial enough differences between them that testing only the latest isn't
adequate. Additionally, some of the testing needs to be done on perls built
with threading, which isn't included on most of the versions available on
Travis. It also is sometimes useful to test without any additional modules
pre-installed like Travis does.
Some idiot has just uploaded a purely spam distribution: THEMA-MEDIA. He clearly knows it's idiotic, because his README.md begins with "CPAN-foolishness".
The documentation requires a bit of work, but from my perspective the implementation is effectively complete. If you're using it, then I'd appreciate any feedback you have before it's "stable" and thus too late to change.
Friends,
I have found certain outward challenges in perl and have always found someways to overcome them. Some of the common challenges i found specific in India are:
India being such a large country have a number of software development centers across it like: Noida, Gurgaon, Bangalore, Hyderabad, Pune etc. Though there are excellent developers in perl but they are less in number and find them sparsely located across these development centers , ie. few in each centers which makes connecting with each others rather difficult. Though there are some perl monger and other groups here but still as the developers are geographically sparsed in India, they dont connect well, eg. a developer in Delhi will not want to subscribe to Bangalore group because he may not find any merit at it. Same is with the recruiters .
My idea is to create a all india perl group, and also list profiles of most of the people here. There will be a weekly or monthly mailer from the group with a list of opportunities , I am willing to use the domain perl.org.in for this and use catalyst for the same.
Also we will plan remote sessions / google hangouts.
Any person here want to comment on this, and / or will want to contribute towards the design / anything just comment here or at https://twitter.com/perl_org_in ?
I tried to get co-maintainer bit for Text::MediawikiFormat, but his e-mail does not get delivered. do you know Derek? Could you help me get in touch with him to become a co-maintainer?