blogs.perl.org

The Interchange Development Group is organizing a conference with the focus on Modern Perl / Dancer / DBIx::Class / Interchange.

We offer you the following incentives:

• From Zero to Hero
• Meet the Experts
• Build the Community
• Write Real World Apps

See act.perl.dance for details.

The conference consists of two days of training (6th and 7th October)
and two days of presentations (8th and 9th October). See program for more
information.

It takes place again at the West Branch Resort in Hancock, NY
(http://www.westbranchresort.com/). If you need assistance to travel there, please let us know.

We are searching for attendees, speakers or trainers and sponsors.

Registration

Call for Papers

Sponsoring

Anyone who has contact to Perl newbies or students, please let me know.
One of the goal of the conference is to introduce new people into Perl, Dancer and Interchange.

Questions and feedback are welcome here or by email.

Regards
Racke

Well in my last post like almost all other XS post I started out by lamenting the sad truth that there was little in the way or resources for XS in 2010 and things haven't improved much since then.

Well I was wrong. While doing a little research for this post I stumbled onto XS-Fun up on github and was so surprised at what I found I decided to do a quick review on it for today's post.

Well it is new tutorial, less than an year old and a work in progress with three short chapters in POD format.

Well it is worth the read as they introduce the novel approach to drop 'h2xs' from the picture and dive right into actually using XS code with practical examples. So to use the authors own words

Eliminating the use of h2xs and bundling any C libraries we use (that we haven't wrote by ourselves) remove a lot of needless complexity.

Still hacking around bash tab completion. Released some utilities like pmpath, podpath, pmless, pmedit (you can find them in App-PMUtils distribution). To use these utilities:

% cpanm App::PMUtils
% complete -C pmpath pmpath ; # this line can be added to your .bashrc
% pmpath [TAB]
% pmpath tex[TAB]
% pmpath text/ansi[TAB]
% complete -C pmless pmless; # do the same for the other utils
(and so on)

You'll notice that I use slash instead of double colon as it should be. And here goes the rant.

Here's the gist of how completion in bash works. For each command, you'll need to issue a 'complete' internal bash command to tell bash how to complete argument for that command. For example:

% complete -W "checkout clean commit log status" examplecmd

After this command is issued, if you type:

% examplecmd [TAB]

or:

% examplecmd c[TAB]

Well I think I will tackle a difficult subject for my next series and that is XS programming or how to add C to you Perl and learn to regret it.

XS programming is not for the faint of heart I will warn you know it is tedious, stressful, unrewarding, undocumented and hard to learn. However if you can get past the first few high hurdles it is well worth the effort.

Now XS programming is not rare you can find it all over CPAN and I can almost grantee if you have ever used Perl to log into a DB then you have used XS.

So it is there and in use every day, it just works and we are happy about that.

In my last article I introduced a design technique called Functional core and Imperative shell (let’s call it “FC&IS”). It enables to do isolated testing without using test doubles (mocks, stubs). It’s also said to produce better designs (I’ll let you judge of that).

My post was a bit abstract and introduced quite a bit of vocabulary. Now I’m going to make it a bit more real by showing some code. Writing this code also helps me re-arrange and crystallize my understanding. Here we go!

Well This should really be the last one in this series baring any big problems that come down the line if people ever end up using this MooseX.

So in my last post I applied the first patch to my MooseX by simply clicking a button on github and I must say I am pleased with the result

So not I get a full green board on CPAN testers for V0.00.05 with 33 passes and 33 attempts however I do see that my compatibility Matrix isn't that broad covering only two OSs.

Looking back a bit comparing to my first result I got 276 attempts, 95 FAILs, 17 NAs 164 PASSes, so I tested on a larger number of boxes but failed a large number of tests.

I’m pleased to announce the release of Box::Calc 1.0, which is an algorithm we’ve been developing for a few years over at The Game Crafter for packing items into boxes. If you run a shipping / receiving operation, or a web store this module can help you determine which box or boxes to use to fit all the items ordered, how much each box will weigh, etc.?

Originally we offered Box::Calc as a web service, but now we’re releasing the full module as open source on CPAN. Enjoy!

[From my blog.]

Honestly I though my last post would be the final one of this rather lenghty series but I was wrong.

Seems soon after my release I got what I think is my first ever 'Pull Request' from github from the resident mooz giiyosewinini na Toby Inkster so I had to post on that today.

Well Seems there is a better fix for the bugs/errors that where thrown in the first version of MooseX::AuthorizedMethodRoles as the root of the problem was the inability of perls less that 5.8.8 to figure out that the $requires part of

 
 foreach my $key (keys($requires))

Well I must of really been up late when I wrote that up as I normally, as force of habit,
wrap my hash refs with {} like this

 
 foreach my $key (keys(%{$requires}))

which might even work with more Perls that 5.8.8 and above. I might have to break out perlbrew and give that a test in another post.