So you need Perl information and the perldoc does not have what you need. First stop the search engine. You type in the keywords and start exploring. One thing I kept noticing with different searches were the results returned that were just the POD online. I decided I was tired of looking at it so I created a Google Custom search that filters out the sites I kept seeing that provided no value.
cpansearch.perl.org
perldoc.perl.org
cpan.org
metacpan.org
ebay.com
amazon.com
The last two kept returning information on Perl books for certain searches when it shouldn't have. Give the custom search a shot and see if it can make your searches noise free too.
The question of what standing job postings have on blogs.perl.org has come up a few times over the lifetime of the site. We discussed it informally among the team, but in the interest of clarity for everyone, we wanted to set something down in writing. These are our rules of thumb:
In general, we welcome job postings put up by developers or other technical members of the team being recruited for. If you want to put up a job posting on this site, chances are high that you are in this group by default. Particularly if you have a say in the hiring process for the job, please feel entirely free to post.
If however you are a HR person or recruiter, may we suggest jobs.perl.org as an appropriate venue to you?
We do not have hard and fast rules for cases that fall outside these clear buckets. Use your judgement; above all, don’t be annoying.
If you really feel unsure about whether your job posting is OK, feel free to get in touch with us directly via email to contact@blogs.perl.org. (Please do not use the comments on this post for this purpose. Among other reasons, you may go unnoticed.)
Our intrepid mapper and OpenStreetMap contributor Wieland has created a
photo walk from the Airport to the venue. It also works as a guide if you arrive by train at the main train station ("Hauptbahnhof").
In the title of
an excellent blog post,
Laurence Tratt calls parsing,
"the solved problem that isn't".
I thought this
phrase captured the current situation
in parsing theory and practice very nicely.
In stating that parsing is not a solved problem,
Tratt realized he was taking on a consensus.
But the consensus is fading --
for example, neither side in the interchange
between
Might/Darais
and
Russ Cox
expresses complete
contentment with the state of the art.
Recently I was reading a program that was using utf8::all and I decided to take another look at the module. The last time I tried it out was version 0.003 from 2011 and it basically did the following:
use utf8;
use open ( :std :encoding(UTF-8) );
use charnames ( :full :short );
@ARGV = map { decode_utf8($_, 1) } @ARGV;
Now autodie did not play nice with use open so that was a blocker for using utf8::all in apps. With the latest version I get use warnings qw( FATAL utf8 ). Looking at the updated POD I see that autodie 2.12 now works correctly with use open. YAY! I have applications using autodie with boilerplate utf8 support and now it is shorter. From this
July was a relatively quiet month for CPAN Testers. Although reports have been flowing, our attentions have largely been elsewhere. Development work behind the scenes is still continuing, but nothing major to report just yet.
Ben Bullock asked on the mailing list, whether he could search other people's test reports? The problem currently with this, is that we don't really expose the reports themselves, except via the CPAN Testers Reports website, when you specifically ask for the report. The reasons for this have largely been because the search of the Metabase still needs to be written. The demand on the current Metabase is expensive, and until we are able to move to the new backend system, we can't afford to expose the results. For the time being the Analysis site covers some of the demands, but Ben's specific needs aren't covered.
In preparing this and my previous blogs, I have noticed aspects where Devel::Trepan could be improved. For this blog, I discovered when comparing Devel::Trepan output with that from a recent perl5db that perl5db sometimes prints several lines of output to try to show a full Perl statement. Devel::Trepan prints a single line — normal in command-line debuggers. However, do see the set auto list command.
As I've done in preparing previousblogs, I then take time from writing the blog to improve Devel::Trepan. Although no one has said anything about this yet in prior blogs, the output you see in the blogs may be a little bit different than what you see if you install from CPAN. However it does match what you will see if you install from the github repository.
But this brings up a couple of other points. First, that one of the reasons that perl5db is probably hard to replace by any debugger is that right now people are still tweaking it.
Life can be strange. Not counting endless transits through Heathrow (presumably some horrid form of karmic justice for a particular wicked former life), I have visited London only twice in the past decade. And offered not a single public class there in all that time.
Yet now I'm lining up for my second London visit, and second series of public classes, in six months. And the first person I have to thank for that is the same person who took care of me in London on my very first visit, over ten years ago now: the inimitable Dave Cross. It was Dave who put me in touch with the wonderful folks at FlossUK, who are bringing me back in October for a second installment of Presentation Aikido, as well as offering my Understanding Perl Regexes class.
As some of you may know, I worked on a partial rewrite of Method::Signatures last year, mainly to add Moose types to the sigs, but also to do some tweaks here and there, and to use it as a base for Method::Signatures::Modifiers (included with MS), which can replace MooseX::Method::Signatures inside MooseX::Declare. This latter reason was the primary goal for me, and I’ve gleefully been using MS, and MSM, in practically all the code I’ve written since. I’ve also ported over a rather large codebase (although admittedly not much of it was using MXD). We’re almost at the eleven month mark since our first release of the new MS, so I thought it might be interesting to check in with how things are doing.
The T-Shirts have finally arrived. Weirdly, some of them
are longsleeved, which we didn't order. But there's no
time to send them back. Maybe you can wear them in winter.
We chose to go for two colors for attendees this year, blue and grey.
I hope you like them. The bright yellow ones are for the organizers,
so they stick out.
The DC PM Podcast has changed hosts. This was due to multiple reasons, but the podcast will reside at the new address for the foreseeable future. The new location is
http://zak.freeshell.org/dcpm/.
I saw a post out in the Blogosphere today about getting weather info from NOAA (The United States National Weather Service). Oh! the horrors of using XML::LibXML or XML::DOM or those other hairy XML modules to get at the data.
The blogger didn't seem to keen on my quick and dirty Mojolicious solution:
I'm returning to Europe next month, and my first stop is in beautiful Lausanne.
I've been visiting that lovely city for several years now for private classes, but
for the first time we have been able to arrange some public training events as well.
We'll be offering the following four classes, with the first three open to the
general public. The fourth is only available to academics of SIB and CUSO
(and is already almost full):
As these are the first public classes we've been able to run in Romandy, I hope that many local Perl users will finally have the opportunity to come along. If you'd like to attend any of these, we'd love to see you there.
You can sign up on the SIB website.
(This post is just a lazy "proof-of-concept" for articles that review modules, but not focusing on comparing similar/competing modules for a task, but on listing various modules surrounding a theme or task.)
So far, this is a short list. You'd guess correctly that more prominent languages like English would have far more tools for it.
Converting number to/from verbage. There's Lingua::ID::Nums2Words for converting number to verbage and Lingua::ID::Words2Nums for converting verbage to number. I've seen far more widespread application for the former task (e.g. 45000 to "empat puluh lima ribu") compared to the latter. Where the former is usually seen in applications that print receipts or cheques, the latter I've only seen used in a script for practising the Indonesian language. Side note: These two modules are actually my first CPAN modules ever, written 13 years ago!
There are two opposing ways to go with any process. Your process can be completely external to the actual distribution so that nothing in the distribution is set up to support the process or its automation.
Or, you can create a process and make your distribution match that.
You choose the one that works for you. Don't jump into something without thinking about the long term consequences. Think about it for the next week, no matter what you are doing, whether at work or during a hobby or whatever you do. What's deciding how you do something?
While I have been on vacation, I have found a little time to add some polish to Galileo, my recently released CMS. Recent additions include a utility for writing a mostly generic configuration file and administrative popups which explain how to create new pages or add new users. The most important thing I have added though is some more setup-time documentation! Hopefully people will now find it even easier to get a Galileo-based CMS up and running.
In writing the documentation, however, I was faced with a question that I do not know the answer to: do any other plack-based or otherwise Mojolicious compatible Perl webservers (i.e. plackup, starman, twiggy etc) support websockets? While in principle a Mojolicious app can run under all of these, Galileo depends heavily on websockets, especially for content editing.
If any of you know, please comment.
I have more ideas for improvements to Galileo, but they will take a little more work than I want to put in here on vacation. In the meantime it is still very functional, go take a peak. :-)
To catch common memory errors you simply have to use the new clang -faddress-sanitizer, along these instructions in perlhacktips.pod or use valgrind.
But to detect race conditions tsan is another gold-mine from google's moscow lab. This is the old valgrind based version:
cd ~/bin;wget http://build.chromium.org/p/client.tsan/binaries/tsan-r4356-amd64-linux-self-contained.sh;chmod +x tsan-r4356-amd64-linux-self-contained.sh;cd -
![image032[1].jpg](https://blogs.perl.org/users/yapceurope_2012/image032%5B1%5D.jpg)
![IMG_4403[1].JPG](https://blogs.perl.org/users/yapceurope_2012/assets_c/2012/08/IMG_4403[1]-thumb-600x450-880.jpg)
