blogs.perl.org

Its still param day here in the Moose-Pen

ok($user->update( $utils->connect(),$container),"update with present container");
$user->reset_conditions();
$container = [{address =>'MNO'},
              {address =>'PQR'},
              {address =>'STU'},
              ];
$user->add_condition({left  =>{ name  => 'username',
                                view  => 'user'},
                      right =>{ value => ['Bill','Jane','Joe']}
                    });
ok($user->update( $utils->connect(),$container),"update array on where param");

Warning! Long read...

This post contains an Arduino Trinket Pro GPS prototype project that only relates to Perl in that all of my knowledge and experience came from my Raspberry Pi Perl work, along with writing C/XS code for several ICs and sensors and making those available as Perl APIs. I'm posting it here due to that relevancy, and because I don't blog anywhere else ;)

To start off, I'll explain a little bit how I got to this path.

I became interested in the Raspberry Pi after a colleague showed me a project he had built with one. I went out, bought a couple and started tinkering. The very first thing I wanted to do was use Perl on it. There were a couple of libraries available, but they seemed convoluted to me, so I wrote my own.

So I’ve learned my lesson. Do not use each().

Always good to read the blogs…

https://blogs.perl.org/users/rurban/2014/04/do-not-use-each.html

Here’s a fun one that caused perl to go into an infinite loop. I suppose being frugal and not assigning things to variables is not necessarily a good idea.

It was 20 years ago (almost) that a group of New Yorkers started Perl mongers. I think at the time we were eating something the caterer for The Perl Conference called "California sandwich" that had sprouts and avocado. In 1997, there was a small core of a Perl community that worked on perl, but there was still room for regular user engagement.

I didn't see this coming. While I was in Amsterdam a couple of weeks ago, Wendy noted that 1997 and 2017 end in the same digit (as does 1967). I don't think we've ever bothered to celebrate an anniversary. I went to check on the date. I registered pm.org on August 22, 1997, which I think makes August 21 the birthday. That was the last day of that conference.

We'll have to do something special guess.

I know that NY.pm will have its anniversary this year, and there my be some other groups. London.pm, when did you start? I think Boston and Seattle was in there very quickly. Who else?

It playing with update and container day here in the Moose-pen.

$container = [Test::User->new({username=>'Bill',address =>'ABC'}),
              {username=>'Jane',address =>'DEF'},
              Test::User->new({username=>'John',address =>'HIJ'}),
              {username=>'Joe',address =>'KLM'},
              ];
$user->update( $utils->connect(),$container);

Usage: Database::Accessor->update( Class , Hash-Ref||Class, Hash-Ref); The $container parameter must be either a Hash-Ref or a Class at …

With new cool TLD's available, I purchased perl dot sydney which is the perfect domain for Sydney Perl Mongers.

Our current/old website is dated and tired, so I also spent some time whipping into shape a new website using GH pages. Having GH pages automagically compile markdown files into HTML is very neat. Plus having everything in github so people can PR, and having group access - are both great. But... that Jekyll isn't Perl does make me feel somewhat sold out, even if it's being used implicitly.

Anyway, please take a look and proof read the perl dot sydney website. Send PR's for all my typos and grammatical errors (people in irc.perl.org's #australia have already gone over it)

Also, if you would like to order one of our Tshirts (which help pay for these vanity domains and our meetup page) - check out the details on our Facebook page.

Read this article on Perl6.Party

As some recall, Rakudo's 2017.04 release was somewhat of a trainwreck. It was clear the quality assurance of releases needed to be kicked up a notch. So today, I'll talk about what progress we've made in that area.

Define The Problem

A particular problem that plagued the 2017.04 release were big changes and refactors made in the compiler that passed all the 150,000+ stresstests, however still caused issues in some ecosystem modules and users' code.

The upcoming 2017.06 has many, many more big changes:

• IO::ArgFiles were entirely replaced with the new IO::CatHandle implementation
• IO::Socket got a refactor and sync sockets no longer use libuv
• IO::Handle got a refactor with encoding and sync IO no longer uses libuv
• Sets/Bags/Mixes got optimization polish and op semantics finalizations
• Proc was refactored to be in terms of Proc::Async

The documentation of Bailador was updated. It looks much better now.

Well is still container day here in the Moose-pen.

package Test::User;
use Moose;
has username => ( is  => 'rw',
               isa => 'Str',);
has address => ( is  => 'rw',
               isa => 'Str',);
1;

A while back I introduced the alienfile recipe system and we wrote a simple alienfile that provides in a CPAN context the tool xz and the library liblzma. I also went over how to test it with App::af. The week after that I showed how to integrate that alienfile into a fully functioning Alien called Alien::xz and promised to show how to then use that Alien from an XS or FFI module. Today I am going to do that. I am also going to show how to use a tool oriented Alien module. (conveniently, Alien::xz can be used in either library or tool oriented Alien mode). If you are more interested in FFI or tool oriented mode feel free to skip down to the appropriate paragraph.

At The Perl Conference in Washington DC, I'll be giving a talk on Modeling a Universe in Perl. For previous versions of this talk, people have asked for more information about how we model complex actions in a (mostly) declarative manner. For example, here's the code for purchasing a clone:

It's the Steps() function which is our declarative code. As you might imagine, there are tons of actions which might require that you be in a particular area, or have credits removed from your wallet, so the Area and Wallet lines can be dropped into any Steps() function anywhere throughout our code. But people want to know how this works. In reality, it's pretty simple.

Well it is look at another module day here in the Moose-Pen.

DBD::DBM::st execute_array failed: 4 bind values supplied but 2 expected [for Statement "INSERT INTO user ( user.address, user.username ) VALUES( ?, ? )"] at …

$dbh->{RaiseError} = 1;        # save having to check each method call
$sth = $dbh->prepare("INSERT INTO staff (first_name, last_name, dept) VALUES(?, ?, ?)");
$sth->bind_param_array(1, [ 'John', 'Mary', 'Tim' ]);
$sth->bind_param_array(2, [ 'Booth', 'Todd', 'Robinson' ]);
$sth->bind_param_array(3, "SALES"); # scalar will be reused for each row
$sth->execute_array( { ArrayTupleStatus => \my @tuple_status } );

Hey everyone,

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

Enjoy!

Portable GitHub system "GitPrep 2.6" is released at 2017-06-10.

Finally, "wiki" system is added. You can write documentation on GitPrep.

At first, Let's try
GitPrep example. You will find GitPrep is real portable GitHub system.

The features of GitPrep

I introduce the featrues of GitPrep for people who see GitPrep for the first time.

• Github clone: GitPrep has the same interface as GitHub. All of repository, pull request, issue, and wiki is used.
• Support issue system
• Portable: You can install GitPrep on your own Unix/Linux server.
• Only needs Perl 5.10.1+.
• Smart HTTP support: you can pull and push repository via HTTP.
• Built-in web server, and reverse proxy support.
• CGI support.
• SSL support.
• Public key authentication support

Installation is very easy. You run only two commands. Difficult settings is unnecessary.

Even if you have troubles by your mistake, for example "git push -f origin master", you can access all of your git repositories directory and fix them.

All reporitories are yours. All repositories exists on your own server.

In this issue:

• Sunday Arrival Dinner
• Tuesday Night Social: Get to know your fellow attendees!
• Tutorials spaces still available
• Call for Speakers: Lightning Talks
• Call for Volunteers

Arrival Dinner - Sunday June 18

Arrangements have been made with Zikrayet Restaurant and Lounge to host a large crowd for The Perl Conference Arrival Dinner.

Given the nature of the place, it will be possible to make this event more of a come and hang out destination than we've been able to have in past years. Just the same we have an official time of 6pm set for the dinner so everyone can have a common plan for arrival.

This is an arrivals dinner but not necessarily the arrivals dinner. It's also a tradition that others who prefer smaller crowds and/or a more vegan-friendly menu organize an Alt Arrival Dinner.

For more information, or to note your intended attendance, please visit: https://github.com/dcbpw/tpc-2017-dc/wiki/Arrivals-Dinner#attendees

Well it get lucky postette day here in the Moose-Pen.

Well I left off yesterday a little worried that I was only testing half of the execute_array as I never actually got down into the DBI code of things. So I decided lets give it a try on that pre-installed 'DBD::DBM' that I used in my '10_crud_basic.t' test case as according to the DBI docs there shold be a defult implimentsion of 'execute_array''

$container = [{username=>'Bill',address =>'ABC'},
              {username=>'Jane',address =>'DEF'},
              {username=>'John',address =>'HIJ'},
              {username=>'Joe',address =>'KLM'},
              ];
$user->create( $utils->connect(),$container);

I've started to build a blog engine in Perl 6 using the Bailador web framework. Primarily as an example for the Bailador book, but if it works well it might even be used as a replacement for the blog engine running blogs.perl.org.

If you are interested, follow the GitHub project. If you'd like to help with the development, let me know, and I'll invite you to the Bailador Slack channel where we can discuss things. If you'd like to support the project financially then the best thing you can do is to back the crowdfunding campaign of my book about Bailador.

NB: The proposed changes have been accepted, there is now a release candidate waiting for your feedback.

A few months ago, I proposed a few changes to Log::Any with the goal of

1. extending the API between applications and Log::Any::Adapters to allow passing hashrefs in addition to the log message
2. allow applications to specify localized context data for Log::Any to add to each log message in that scope
3. allow system owners to globally specify a default adapter other than Null

To get the bigger picture, you might want to revisit the original blog post and the reply by dagolden.

Based on the follow-up discussion on- and offline, I've tried to come up with a pull request that implements the proposed changes. To give it a try, clone it, and use my sample adapter to produce some output:

Check out our super-cool schedule, which links to talk and speaker details, at http://www.perlconference.us/tpc-2017-dc/schedule/!

The conference is a few weeks away (June 19-21 for the core conference, 18th and 22-23 for tutorials), so be sure to register and we'll see you soon!