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).
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.
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.
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
* 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
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:
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.
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.
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
After a long incubation period of intermittent hacking, I am pleased to present Perl hackers worldwide with the option to quickly and easily print to their console screen.
Ok.. why?
From the module's README:
Terminal::Print intends to provide the essential underpinnings of command-line printing,
to be the fuel for the fire, so to speak, for libraries which might aim towards 'command-
line user interfaces' (CUI), asynchronous monitoring, rogue-like adventures,
screensavers, video art, etc.
Let's first point out that this module is a serious attempt at solving a relatively frivolous problem. There are plenty of existing text display engines (hello, ncurses!), game engines, and other Perl modules that already solve many command line display (CLD) issues.
However: ncurses is not re-entrant. Furthermore, its UTF-8 support is (understandably) bolted on. Looking around at other C library options, it came to dawn on me: why was I involving "native" options, anyway?
With the latest stable release of perl, v5.24.0, you could easily get trapped into using a problematic combination of math modules.
Here is how, and what you should do to avoid trouble.
Well there still lots of life in the a little Moose-Pen today seem I still have plenty of poop to cleanup.
Well in my last post I cleaned up a little moose poop and today I am going to take a major step forward and clean up allot more. So far most if not all the poop I have been generation comes from my efforts of either
Having required attributes
Coercion into classes or
Type errors
Well one would think there will be a large amount code to cover in a single post but thanks to Moose I really only have to add
I'm back from Romania and had a lovely time at YAPC::EU, er, The European Perl Conference, er, or this:
I unveiled that suggested logo at my opening keynote only to discover that many Perl devs had no idea what I was talking about. My sense of humor is shouting "get off my lawn."
However, I gave a lightning talk announcing Veure, including the game's name and blog! Veure is officially known as Tau Station and sign up for our newsletter to find out more, including keeping up with the alpha. Or just read our blog to see what's happening with it (but you really want to sign up for that newsletter).
Many thanks to Evozon for hosting a great conference!
I would like to announce the release of version 0.2.1 of CamelHarness.js - a small JavaScript library that can start Perl5 scripts from applications based on Electron or NW.js. I will be happy if someone finds it useful!
