blogs.perl.org

Well there comes a time in every playpen where it is time for bed so this will be the last moose-pen for a little while as I am all out of Moose to do on my Accessor project and I have to start getting it ready for CPAN.

So my love affair with Moose is ending, for the time being, and now I start working on the part of creating packages I dread the most 'Distribution'.

Up to this point in my career I have been lucky the only complex CPAN dist I ever worked with, DBD::Oracle, came with an extensive MakeFile.PL that I really only need to tweak every once an a while. At some 2800+ lines of code I was glad for that.

I have some FASTA files with headers like this:

>gi|83274083|ref|AC_000032.1| Mus musculus strain mixed chromosome 10, alternate assembly Mm_Celera, whole genome shotgun sequence

I wanted to extract just the 2nd field, so here's a Perl 6 script to do that:

In what is a somewhat mild case of yak-shaving, I need a portable way of identifying file types in several situations. For example, when indexing files for Dancer::SearchApp or when handling user uploads, I want to somewhat reliably identify various files. I want to determine their type without trusting what the user tells me they are, and I also want to send the appropriate Content-Type header when serving files again.

It is a pleasure to announce that this year the Perl5 Porters Hackathon (http://p5h.org/), held between the 11th to 14th November in Amsterdam, will be hosted by Booking.com and officially supported by The Perl Foundation.

The P5P Hackathon is a seeding event for the essential work done inside the Perl core. It functions as a symposium where current, and future, Perl5 hackers can meet and cross-pollinate ideas that may develop into significant future evolution.

This year the Hackathon has three major aims:

• The sharing of knowledge. This will be facilitated by talks of up to twenty minutes to share information about any field with which the speaker is intimate.
• To facilitate open discussion. Free participation in conversations regarding important topics you or someone else suggests.
• Hacking the Code: Working on specific problems in order to reach tangible results.

The Hackathon will take place within two different locations in Amsterdam at Booking.com offices, both locations are within a short walk of each other.

So in honour YAPCE 2018 it's shiftin bobbins day here in the Moose-pen.

Carrying on from where I left off in yesterday's post I decided it was time I cleaned up a little more of my code. Seems I do this

use Moose;
    with qw(Database::Accessor::Roles::Base
      Database::Accessor::Roles::Comparators);
    use MooseX::Aliases;
    use MooseX::Constructor::AllErrors;

or code similar to it a almost a dozen times in the Accessor.pm file. Now there is nothing wrong with this but I think I can clean it up a bit by a just a little re-factoring or shifting things about (hence the link at the top).

The link of the project

You may Download presentation or view short video

The main feature of new debugger is debugging debugger commands. Yes you may debug itself (reentrance is not limited). This mean you may extend debugger easily. That is possible because of state of each debugger "copy" is saved in special array accessible through $DB::state

To enable debugger debugging (dd) you turn on this state then run command, you want to debug, after that. Example how to enable debugging debugger command 'step over' (n):

DB::state( 'dd', 1 );
n

Besides new debugger you get the new method to debug scripts and may forget about debugging by 'print' statements.

Now you just put special comment: #DBG: EXPR #

2+ years on since I wrote "Toolkit review: Devel::Local, Devel::SimpleTrace, Reply" and I've got a couple more suggestions. I still use Devel::Local a lot but for something more substantial than quick hackery I use mst's App::Myperl.

I don't use Devel::SimpleTrace much anymore.. I switched to Devel::Confess since watching haarg talk about writing it in a video that I can't find right now. Lastly I still use Reply but I've added Toby Inkster's Pry to my secret weapon list. It makes dropping into a Reply interactive session super easy. (Use pry; pry();)

I am pleased to announce that Enlightened Perl Organisation (EPO) has kindly extended the support of Strawberry Perl project by sponsoring our build server (VPS) for the next 12 months. I would like to thank Mark Keating for arranging the funding.

For those interested in technical details: the build server is MS Windows 2012 R2 virtual private server, 4 CPU, 16 GB RAM, 120 GB HDD.

If you are also considering supporting Strawberry Perl project you can do it indirectly by becoming EPO member or via donating EPO.

Yep. You guessed it. Yet Another Moose Post. Today in the Moose-Pen just a quick bit of code cleanup

I stumbled upon some of my early notes for this project today and it seems I forgot to include a MooseX I was keen on using from the beginning, I guess I forgot about it, so a little back programming today.

The MooseX is called ' MooseX::AlwaysCoerce ' and it does what it says, forces all of your attributes to have

coerce   => 1,

unless you set them to

coerce   => 0,

Top Ten Things You Need To Know about Perl 6
[The description says 2 hours, but we agreed to 3 over email, I'll get it straightened out. They also got the title from my upcoming OSCON London talk instead the intro, but we'll straighten it out.]

As the title says, I'm working with O'Reilly to deliver a 3-hour training seminar on the basics of Perl 6 in mid-October. This is going to be more targeted to those learning Perl 6 ab initio, rather than seasoned Perl 5 programmers. I do intend to throw a few notes in for current Perl hackers, especially ideas on how to migrate your existing Perl 5 code to Perl 6 in a reasonably painless fashion.

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week. Enjoy!

p5p pumpking David Golden wrote the following topic.

Comparison of Class::Tiny and Object::Simple

I'm pleasure he is interested in Object::Simple even if the entry criticize Object::Simple.

----------------------------------------
Yes, you can create custom constructors, but that defeats the syntactic simplicity of Object::Simple.
----------------------------------------

No, No. Custom constructor is very very easy. Nothing is difficult.

-------------------------------------------
Very soon, you'll have re-invented the semantics of BUILD/DEMOLISH.
-------------------------------------------

No, No. Perl calls constructors and destructors in correct order if we use only single inheritance.

I strongly recommend single inheritance in object-oriented programming.

See Object::Simple(CPAN) for more details. I add FAQ section to reply this question.

Well the Moose-Pen is not dead yet as I still found some Moose to blog about, and I though I was so close.

On thing that really bugs me about Perl is the fact you can have a lovely interface like this

  my $thingy = $object->get_some_thing();
  $object->set_some_thing(“Not my thing”);

and then some smarty-pants RFB comes by and does this

  my $thingy = $object->{some_thing};
  $object->{some_thing} = 'Not my thing';

Anyone who ever comes from a OO background say in Java or even C# usually can be heard screaming into the halls of a Perl shop cursing the very day Larry said “let's create some disruption” and have 'c' with types.

As part of a demo/POC I hacked together a complete Perl binding for the Docker Engine remote API v1.24 (Docker Engine 1.12).

We are sadly not using Perl where I currently work so after demoing some stuff we will move forward using other tech.

There exist some modules on CPAN already but they are not complete and did not work with the new features in Docker.

Perhaps if someone wants to continue the work they can fork and/or merge with the other modules to create a definitive Perl binding for Docker.

Here is the project

* No support will be given
* Rewrite needed
* Look at the Golang binding for ideas for the next steps, eg. types instead of handling everything as JSON

Recently I've started a new interview series published both as videos and as a Podcast.
The first 3 episodes were with Perl developer: Jason Crome on Dancer 2, Sawyer X on Perl 5 Porters, and Joel Berger on Mojolicious

The 4th episode is Tom Hudson on gron that helps making JSON structure grepable.

I have uploaded videos from the first day of the Alpine Perl Workshop (Innsbruck, 2016): https://www.youtube.com/channel/UCLsVz9vprzs6U6PmcI4tnqA. The second day of videos should be done uploading by the same time tomorrow. Some observations from recording/processing/uploading the videos:

Today in the Moose-Pen I am going to solve a little problem with Moose.

So cleaning up a lot of Moose poop over the last few days and part of that effort is to ensure some of my proposed features with this post. Now I have re-factored that a little today into this sub

Do you need "Fast Perl"? Look at "Static Perl" project at once.

Static Perl - Fast calculation, parallel process, GC, static typing, VM with perlish syntax without XS

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week. Enjoy!

Dancer2 0.203001 is on its way to a CPAN mirror near you. It is essentially a maintenance release, with only two minor changes:

• Class::Load was replaced by Module::Runtime. This will result in a slightly faster execution time for your Dancer2 apps. This had been applied previously, but was erroneously undone by another commit. Thanks to veryrusty for noticing and fixing!

• The minimum version of List::Util needed by Dancer2 was omitted from 0.203000, causing some headaches for users of older versions of List::Util.

The full changelog follows: